JReleaser 0.10.0 is the last push towards 1.0.0. We'll concentrate on bug fixing and polishing from now on. This realease brings the following updates:

JPackage: The jpackage tool can now be used to assemble distributions of type NATIVE_PACKAGE. You have the choice to reuse an existing jlink assembler or supply a runtime image created by any other means.

Archive extensions: Additional archive extensions are now supported, such as .tar.xz, .txz, tar.bz2, .tbz2. Additionally, both jlink and nativeImage assemblers now let you specify the archive format to use, with .zip as by default.

Platform replacements: JReleaser defines a fixed set of platform values (such as osx-x86_64 or linux-aarch_64) which are used to identify platform specific artifacts. These values are ofthen times added to artifact names. Sometimes you'd like to use a different value such as mac-arm64 or linux-amd64. You can use platform replacements to achieve this goal.

Artifactory: JFrog's Artifactory supports multiple types of repositories such as generic, rpm, deb, nuget, and more. Previously you could only configure a single generic repository, now you can configure multiple repositories of any type as needed.

Gofish: The GoFish package manager joins the set of support packagers. You can use it with distributions of type BINARY, JAVA_BINARY, JLINK, and NATIVE_IMAGE.

Spec: You can use this packager with distributions of type BINARY, JAVA_BINARY, JLINK, and NATIVE_IMAGE.

Chocolatey: You can use this packager with distributions of type BINARY, JAVA_BINARY, JLINK, and NATIVE_IMAGE.

Macports: You can use this packager with distributions of type BINARY, JAVA_BINARY, JLINK, and NATIVE_IMAGE.

JsonSchema: The CLI offers a new command that generates a json-schema file, useful for validating JSON, YAML, and TOML config files.

🚀Changelog 📝Milestone