Repository navigation
Gradle Plugin Portal #490
Description
We should publish the JavaPackager gradle plugin to the gradle plugin portal so that users can register the plugin with
plugins {
id("io.github.javapackager") version "x.y.z"
}
Per https://docs.gradle.org/current/userguide/publishing_gradle_plugins.html it looks like we are more or less already set, we just need to register an account and call the publishPlugins task as part of the publication process (and maybe add/adjust a piece of metadata or two in the existing gradlePlugin config
Activity
Use the plugins block in the README's Gradle setup (#490)
fvarrui commentedon Oct 5, 2026
Good news: this already works without publishing to the Portal.
plugins.gradle.org/m2redirects artifacts it doesn't host to Maven Central (HTTP 303), so with2.0.0-rc1a project with nopluginManagementat all resolves and applies the plugin with just:plugins { id 'io.github.javapackager' version '2.0.0-rc1' }(tested with an empty Gradle user home). It works now that the launch4j Gradle plugin is no longer a dependency in the POM (#444), so nothing has to come from the Portal itself.
The README still showed the old
buildscript/apply pluginsetup; it's updated indevelfor 2.0.0. Publishing to the Portal would still make the plugin show up in its search, so I'd keep this open as a low-priority enhancement. What do you think?Record #490 answer