3 posts tagged with "jpos-ee"

We are pleased to announce the release of jPOS 3.0.2 and jPOS-EE 3.0.2, available as of September 30, 2026.

These releases bring together several months of work on security, transaction observability, modern message formats, and operational reliability. jPOS strengthens the core messaging and Q2 runtime; jPOS-EE builds on that foundation with improvements to QRest, database transactions, cryptographic services, and supporting infrastructure.

Although the version increment is small, the changes are substantial. This is also a release worth planning for: the Java baseline advances, some APIs have been removed, and log consumers need to accommodate a more structured event model.

The best jPOS version is usually the latest one.

That may sound counterintuitive if your organization treats -SNAPSHOT as a synonym for "unstable", but that is not how we operate jPOS and jPOS-EE. We work hard to keep the latest snapshots production-ready. We run them in production ourselves. They are where the current fixes, optimizations, dependency updates, security improvements, and newly certified behavior land first.

In practice, the latest snapshot is often the most advanced, optimized, and feature-rich jPOS version available.

Following the same branch model we adopted for jPOS last December, jPOS-EE is now aligned with JEP-14 — The Tip & Tail Model of Library Development.

The rename is straightforward:

• The next branch (jPOS-EE 3.x) becomes main — the tip, where active development happens.
• The master branch (jPOS-EE 2.x) becomes tail — the stable series, receiving only critical fixes.

REQUIRED ACTIONS​

On your existing next branch:​

git branch -m next main
git fetch origin
git branch -u origin/main main
git remote set-head origin -a

On your existing master branch:​

git branch -m master tail
git fetch origin
git branch -u origin/tail tail