CurseForge Gradle Publish Plugin vs Vineflower

CurseForge Gradle Publish Plugin publishes build artifacts to CurseForge from a Gradle build. A publication can specify a CurseForge project ID, main artifact, game versions, display name, release type, changelog, and artifact relationships. It uses the CurseForge Upload API and needs an API token in the plugin’s curseforge extension. The README warns that keeping the token in a version-controlled build script can expose it; user-specific Gradle properties are suggested instead.

For mod projects, the plugin can derive publication details from other tools. With Fabric Loom and a remapJar or jar bundling task, it can create a publication preconfigured for Fabric and the targeted Minecraft version. Its ModDevGradle and NeoGradle integrations can infer NeoForge and Minecraft-version details. When Gradle’s java-base plugin is present, it infers the Java version from the compileJava target.

Vineflower is a free, open-source Java decompiler for producing readable code from Java classes. It supports modern Java, including J21 and later, with automatic reformatting and multithreaded decompilation. The main distribution is a JAR from GitHub releases and Maven Central. You can run that JAR from the command line with archives or files, saving output to an archive or folder or printing it to the console. Vineflower can also be added through Maven or Gradle, and an IntelliJ plugin is available. A command-line option can emit Kotlin classes as Kotlin; the full distribution includes an experimental Kotlin decompiler plugin and other plugins for IntelliJ IDEA annotations and variable renaming. A slim artifact omits built-in plugins. Running requires a Java 17 or newer JVM. An experimental plugin system supports output changes or new JVM languages. The project calls itself a work in progress and welcomes contributions. It is licensed under Apache-2.0.