Author: aalmiray

Releases posted in 2021

Posted on by aalmiray

The year 2021 is now behind us and what a year it was. Sometimes I could not keep listening to the news, once you feel the grip of depression you must act quickly to get out of the downward spiral. When that happened I turned my attention to code. Fortunately at work together with my teammates we had a series of success stories and wins all year long, yay for us! Now on the side of personal projects I did not manage as many releases as last year, 59 this years vs. 98 last. Or did I? Back in late Read More

Releasing Rust Binaries with JReleaser

Posted on by aalmiray

You’ve spent some time working on that Rust project of yours and are now ready to post a release. It’s quite straight forward to build and upload binaries as assets to a Git release but let’s face it, we can’t expect consumers to find the release page, select the appropriate binary for their platform, download the file, and configure their environment settings to point to the new binary. Well yes, some people like to do that but most prefer to use a tool instead, something that automates the steps just described, something like a package manager such as Homebrew, Snapcraft, Read More

JReleaser 0.10.0 has been released!

Posted on by aalmiray

JReleaser v0.10.0 has just been released! It is the last push towards 1.0.0. We’ll concentrate on bug fixing and polishing from now on. Be mindful of the breaking changes introduced in this release. There are plenty of improvements in several areas, a quick summary of the highlights follows: 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, with most packagers and Read More

JReleaser 0.9.1 Released!

Posted on by aalmiray

JReleaser v0.9.1 has just been released! This is our first fix point release as a bug fell through the cracks preventing distributions of type NATIVE_IMAGE to be successfully assembled using JReleaser’s Native Image assembler or just packaged with any of JReleaser’s supported packagers. We encourage everyone that has moved to v0.9.0 and requires NATIVE_IMAGE support to upgrade to v0.9.1 at your earliest convenience. There are also a couple of additions in this release (full list of changes found here): CalVer Because there’s more than one way to version your project and sometimes SemVer is not enough, CalVer is now also Read More

JReleaser 0.9.0 has been released!

Posted on by aalmiray

🚨 UPDATE 🚨 Please upgrade to v0.9.1 instead! JReleaser v0.9.0 has just been released! JReleaser v0.9.0 is a big update as we gear towards v1.0.0. Plenty of improvements were added to this release to make it the best one so far. Be mindful of the breaking changes introduced in this release.There are plenty of improvements in several areas, a quick summary of the highlights follows: Jlink We’ve made several improvements to the Jlink assembler. In particular it’s now possible to create a Jlink image for Quarkus applications using their fast JAR layout. You’ll find an example at the project’s documentation. Read More

JReleaser 0.8.0 has been released!

Posted on by aalmiray

JReleaser v0.8.0 has just been released! This release closes all required items in the v1.0.0 roadmap, opening the door for v1.0.0 to be released next after polish and housekeeping items are taken care of. There are no breaking changes in this release however be advised that v1.0.0 will remove all deprecated code thus please update your configuration as soon as possible. There are plenty of improvements in several areas, a quick summary of the highlights follows: Internationalization All modules have been retrofitted with internationalization support. In particular the CLI tool has been translated to English, German, French, Italian, Brazilian Portuguese, Read More

JReleaser 0.7.0 has been released!

Posted on by aalmiray

The latest JReleaser release, v0.7.0, is out! This is a smaller release compared with previous ones as core features are mostly complete. There’s a single breaking change in this release and should concern you if and only if you make use of the JDKs Gradle plugin. Here’s a quick summary of what’s new: Homebrew In v0.6.0 for distributions of type BINARY, that is those that provide executables regardless of their source language, Homebrew would automatically generate a Cask instead of a Formula and would not give you a chance to make it the other way. Now in v0.7.0 you’re back Read More

JReleaser 0.6.0 has been released!

Posted on by aalmiray

JReleaser v0.6.0 is out and about! There are a total of 64 items listed in the v0.6.0 milestone, please be mindful of the small set of breaking changes brought by this release. There are plenty of improvements in several areas, a quick summary of the highlights follows: Homebrew Several updates were made to the Homebrew packager. To begin with, artifacts that target both OSX and Linux can now be used in the same Formula. The binary stanza is also supported in Casks, giving you the option to install a .zip artifact. The appcast stanza is supported in Casks as well. Read More

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

ˆ Back To Top