Crafting rolling releases for a Quarkus CLI application

Posted on by aalmiray

I’ve been working on a tool called JReleaser for sometime now. JReleaser shortens the distance between your binaries and potential consumers by packaging and publishing said binaries using formats and tools that consumers enjoy, such as Homebrew, Scoop, Docker, etc. All kind of Java (and since v0.5.0 also non-Java) applications are supported, this being said CLI applications are ideal. There are many ways to build CLI applications with Java, it so happens that Quarkus is one of them. I’ve been looking for an excuse to setup a Quarkus project to try out JReleaser with it, little did I know that Read More

A year of Go

Posted on by aalmiray

Last year I blogged about Jumping into Go. I did it because I wanted a CLI tool that would let me invoke Maven or Gradle builds using their respective command wrapper or the actual command. This tool is known as Gum. Decided to write it in Go because a) the tool is CLI and would need platform specific hooks, b) Go produces small binaries for all target platforms, and c) to force to me actually learn and use the language. As explained at the first post my experience with Go was quite similar to what I went through when I Read More

JReleaser 0.5.0 has been released!

Posted on by aalmiray

The latest JReleaser version is out! v0.5.0 is readily available for download. As always, this release is comprised of bug fixes and new features listed at v0.5.0 milestone. Please take special note of the breaking changes introduced in this release. Version 0.5.0 introduces 2 additional distribution types, 2 additional announcers, and refinements over Jlink and NativeImage distributions. A quick summary of what’s now available follows: Generic Binary Distributions JReleaser supports Java binary distributions since its first release, however this new type allows JReleaser to package and publish non-Java distributions, the only requirement is to follow the standard Linux binary distribution Read More

JReleaser 0.4.0 has been released!

Posted on by aalmiray

I’m ecstatic to announce that JReleaser v0.4.0 is readily available! This release brings a host of features and bug fixes that should make your release process snappier and customizable. Take special note of the breaking changes introduced in this release, as always all features and fixes are collected in matching milestone. Starting with this release there are now 4 cross-platform Java Runtimes to help you get started: Mac OSX, Windows, Linux (glibc), and Linux (musl). Here’s a quick recap of the new features available in this release: Additional Git Releasers GitHub, GitLab, and Gitea are supported since the first JReleaser Read More

JReleaser 0.3.0 has been released!

Posted on by aalmiray

Another two weeks have passed since release v0.2.0 and now I’m happy to say that release v0.3.0 is readily available! This version brings lots of improvements to existing features and adds a few more. Take special note of the breaking changes; the v0.3.0 milestone shows the full list of updates and fixes. Perhaps the most important change found in this release is the option to run JReleaser without needing a Java runtime before launching. Cross-platform Java Runtimes JReleaser 0.2.0 added an the ability to assemble cross-platform Java Runtimes with Jlink; given that JReleaser releases itself it should be no surprise Read More

JReleaser 0.2.0 has been released!

Posted on by aalmiray

With just two weeks since its first release, JReleaser has posted its second release: 0.2.0 is here! This version is an overhaul of the whole tool across the board, as shown by the list of issues associated with the v0.2.0 milestone. There you’ll find bug fixes, small features, and big features, some of them which will be described in the following paragraphs. Auto Config Releases The original idea behind JReleaser is to publish Java binaries via several distribution channels, such as Homebrew, Snap, Scoop, etc. These distribution channels typically require downloading artifacts from a Git release page, which is why Read More

JReleaser says hello!

Posted on by aalmiray

I’m beyond ecstatic to announce that JReleaser has finally posted its first release! JReleaser 0.1.0 is readily available, you can find more about this tool at https://jreleaser.org. So what is JReleaser? In just once sentence: the quick and effortless way to release your Java project! For 2 decades we have relied on Maven Central as the de facto place for publishing JARs, however options for publishing binary distributions (such as Zip and Tar) abound, often times tied with specific platforms such as Homebrew for Mac, Snapcraft for Linux, and Scoop for Windows, among others. JReleaser’s goal is to lower the Read More

Revisiting Publication to Maven Central with Apache Maven

Posted on by aalmiray

Some weeks ago I posted an entry on Publishing to Maven Central with Apache Maven which shows the configuration I put in place on a handful of Open Source projects I maintain. The trigger that starts a release workflow is a commit message with “[release]” as a prefix. I was quite happy with the results, after all I’ve got the whole release pipeline working on automatic, however two things were nagging me. Firstly that a release workflow would always require a commit. What if I just wanted to publish a release on the go? Add up pushing a release from Read More

PomChecker 1.1.0 has been released!

Posted on by aalmiray

I’m happy to announce the immediate availability of the PomChecker suite version 1.1.0! PomChecker is a small utility that can verify if a POM or BOM file complies with the minimum requirements for being uploaded to Maven Central. I wrote this utility to reduce the chance of getting an error when uploading artifacts to Maven Central due to invalid or missing information in a given POM. There are no changes in behavior compared to version 1.0.0 however there are now three more options at your disposal for checking the validity of a POM file. The new options include: Running as Read More

Publishing to Maven Central using Apache Maven

Posted on by aalmiray

Last week JFrog announced changes to its Bintray & JCenter services which will eventually lead to these services being discontinued by February 2022. I’ve been a happy Bintray user since the early days. Their services make uploading archives and making them available to the public a snap. Syncing those artifacts from JCenter to Maven Central can also be automated, simplifying the full release process. Previously I blogged about the options available to Gradle projects for publishing to Maven Central via Bintray. I’m saddened by the recent news of Bintray riding into the sunset, I’ll miss it dearly. And like many Read More

ˆ Back To Top