From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

``java-library`` doesn't hurt either, though

I think kotlin applies it under the hood, so there is no difference

not quite: it applies `java`, which does a bit less than `java-library`

see <https://docs.gradle.org/current/userguide/java_library_plugin.html> for what `java-library` adds over `java`

IMO the biggest thing is
&gt; A feature of the `java-library` plugin is that projects which consume the library only require the classes folder for compilation, instead of the full JAR. This enables lighter inter-project dependencies as resources processing (`processResources` task) and archive construction (`jar` task) are no longer executed when only Java code compilation is performed during development.

interesting. okay. so maybe doesn't seem all that terrible to just keep both. /shruggie