Gradle vs Neo-Loom

Gradle Build Tool is a free, open-source system for automating software builds across projects of different types and sizes. Build logic can use either Kotlin DSL or Groovy DSL. Incremental builds, caching and parallel task execution support the build process, while Gradle downloads and manages transitive dependencies from Maven- and Ivy-compatible repositories. The Gradle Wrapper can provision a build environment and specify the Gradle version used by a project. Its ecosystem covers JVM, Android, C/C++, Swift, Objective-C and assembler projects, and it runs on Windows, macOS and Linux. The Tooling API lets IDEs and other tools inspect projects, run builds, receive progress events and cancel operations. Listed support includes Android Studio and Ant, plus Checkstyle, CodeNarc, PMD and JaCoCo. Gradle includes dependency verification. The maker says open-source security fixes are limited by its end-of-life policy; its Security Subscription offers prioritized fixes under SLA and extended maintenance, but does not guarantee a clean scanner report when findings come from third-party libraries.

Neo-Loom is a free Gradle plugin for Minecraft mod development environments using NeoForge or MinecraftForge. It is a fork of Fabric Loom and is heavily based on Architectury Loom. Implemented support includes NeoForge 1.21+ and MinecraftForge 1.20.1+. The plugin supports multi-loader projects, dependency management, client and server scope, and dedicated server support. It provides run configurations for NeoForge and MinecraftForge covering server data, client data, and game test server environments. Neo-Loom supports Jar-in-Jar packaging, converts ClassTweaker or AccessWidener files to AccessTransformer format, and supports publishing and consuming ModDevGradle-compatible Access Transformers and Interface Injections. Devlaunch is listed as implemented. Setup uses the Fabric and RelativityMC Maven repositories and the Gradle Plugin Portal, with plugin IDs shown in the README. The repository is MIT licensed and points users to Discord for support. Listed unfinished work includes JUnit, production launch tasks, and split-source, client-only, and server-only setups for (Neo)Forge.