Releases posted in 2022

Posted on by aalmiray

2022 is in the books. And what a year it was. We thought 2022 and 2021 were enough well, we know now 2022 topped them many times over. Work wise many teams at my current employer went the extra mile to ensure the next version of our flagship products will be ready for shipping this year as scheduled. Can’t wait to tell you what’s coming. Watch this space in the coming months. How well did I do this year with personal projects? Managed to post 59 releases in 2021 and in 2022 I managed … 59 again 😛 However, I’m Read More

JReleaser 1.4.0 has been released!

Posted on by aalmiray

JReleaser v1.4.0 has just been released! The full list of issues can be found at the v1.4.0 milestone. This release adds a new distribution type (FLAT_BINARY), a new assembler (java-archive), updates to Docker support, and more! This release includes contributions made at Luzern Hackergarten as well as Hack.Commit.Push. Distribution New flat-binary distribution may be used to release binaries without packaging them in archives. Several package managers support this new distribution type. Deployment Adjustments to Nexus2 support now let you deploy snapshot artifacts to Nexus2 servers and Maven Central. Few other updates were made to support multi-project deployments and projects without Read More

Jarviz 0.1.0 has been released!

Posted on by aalmiray

I’m excited to announce the first Jarviz release. v0.1.0 is here! What is Jarviz you may ask, it’s a brand new CLI tool that can inspect JAR files and provide insight on their contents. I build tools as a hobby. Some of these tools require Java 8 as a baseline because consumers may not have upgraded to recent versions of Java. As such tools must ensure their dependencies are compatible and do not contain bytecode higher than 52 (Java 8). I use the EnforceBytecodeVersion rule for Maven or Gradle given the build tool of choice for a particular tool. Yet Read More

JReleaser 1.3.1 has been released!

Posted on by aalmiray

JReleaser v1.3.1 has just been released! This is quick fix release given a pair of issues found with deployment to Maven Central, recently releases in v1.3.0. We decided to cut a quick release now instead of waiting for the next stable release (1.4.0) by the end of December 2022. The full list of issues can be found at the v1.3.1 milestone. Maven Central Deployment to Maven Central is performed by the Nexus2 deployer. Operations that modify the state of a remote staged repository (close, drop, release) may take some time depending on the size of the repository. JReleaser v1.3.1 adds Read More

JReleaser 1.3.0 has been released!

Posted on by aalmiray

JReleaser v1.3.0 has just been released! This release delivers a feature that has been requested since the first news of JReleaser came to light: posting releases (JARs & POMs) to Maven Central. Yes! We finally have it! The full list of issues can be found at the v1.3.0 milestone. This release includes contributions made at Basel & Luzern Hackergartens as well as Hacktoberfest. Here’s a quick rundown of the new features: Deploy There’s a new deploy phase available in the workflow. This phase is responsible for uploading artifacts to locations that follow a particular layout. This new phase supports Maven Read More

A POM by any other name

Posted on by aalmiray

By POM I mean Apache Maven’s Project Object Model. The POM format is widely used not just by Apache Maven to build and consume projects, but also by other tools such as IDEs, build tools, code analyzers, etc. Understanding the capabilities exposed by this format are key to successful builds, developer productivity, supply chain management (and security as well), and other concerns. What follows is a list of different types of POMs you may encounter in the wild. This list is not exhaustive, feel free to comment on other patterns you may find. To begin with, a pom.xml file is Read More

JReleaser release cadence

Posted on by aalmiray

Since the early days JReleaser has had 2 release paths: fast & slow. The fast path is the early-access release, posted every time a commit is pushed to the main branch. This type of release allows early adopters to test out new features as soon as they are added to the main branch. Consumers of the jreleaser/release-action GitHub Action can take advantage of the version property exposed by said action to select this release. Early Access releases are intended to be downloaded manually as they might be unstable and as such only CLI related artifacts are posted. There are NO Read More

JReleaser 1.2.0 has been released!

Posted on by aalmiray

JReleaser v1.2.0 has just been released! I’m quite excited about this release as it brings a feature that’s been brewing for a long time, even before 1.0.0 came out: execution hooks. But, wait there’s more! The full list of issues can be found at the v1.2.0 milestone. We’ve also merged contributions from 4 new contributors: Margarita Nedzelska, Alexius Diakogiannis, Guillaume Smet, Aiden Turner. Execution Hooks JReleaser follows a series of steps when creating a release. Command hooks let you invoke external commands before and/or after each step is executed. With this feature in place you may invoke arbitrary commands that Read More

JReleaser 1.1.0 has been released!

Posted on by aalmiray

JReleaser v1.1.0 has just been released! This is the first feature release after v1.0.0 and it comes with a few goodies. The following sections describe new capabilities offered by this release. Download One of JReleaser’s core tenets is enabling releases to be posted from a local environment as a complement to performing this task at a CI or remote environment. For this to work all behavior configured on CI must also be available on a local environment. The newly added Download step lets you download files (assembly assets, templates, etc) from different sources such as FTP, HTTP, SCP, and SFTP. Read More

JReleaser 1.0.0 is here!

Posted on by aalmiray

The day has come. JReleaser v1.0.0 is here! I’m beyond ecstatic to post this announcement as this release is the culmination of multiple efforts made by all contributors, taking into account feedback received by several early adopters, some of which can be seen here. Remember that all deprecated code has been removed, we recommend upgrading to v1.0.0-M3 first to find out if your build uses deprecated features before moving to v1.0.0. There is one more thing to mention, this release coincides with v0.1.0 which was posted exactly 1 year ago 🥳🤩 Lots of features have been added to the tool Read More

ˆ Back To Top