Skip to content

chore(deps): bump artemis-jakarta 2.44.0 → 2.54.0 and migrate groupId to org.apache.artemis#24049

Open
stian-sandvold wants to merge 1 commit into
2.42from
fix-artemis-groupid-2.54
Open

chore(deps): bump artemis-jakarta 2.44.0 → 2.54.0 and migrate groupId to org.apache.artemis#24049
stian-sandvold wants to merge 1 commit into
2.42from
fix-artemis-groupid-2.54

Conversation

@stian-sandvold
Copy link
Copy Markdown
Contributor

What

Bumps artemis-jakarta.version from 2.44.0 → 2.54.0 and migrates the Artemis Maven groupId from org.apache.activemq to org.apache.artemis.

This supersedes the Dependabot PR #23903, which bumped only the version. That bump fails the unit-test check because of the groupId change described below — so the version and the groupId need to move together.

Why the groupId change is needed

Apache Artemis became its own Apache top-level project and migrated its Maven coordinates from org.apache.activemq to org.apache.artemis starting in 2.50.0. The old coordinates are still published, but only as relocation stubs that point at the new ones.

The consequence: with just the version bump, we still declare org.apache.activemq:* while Maven resolves the relocated org.apache.artemis:* artifacts. dependency:analyze then fails the dhis-support-artemis module — it sees the new coordinates as "used but undeclared" and the old ones as "unused declared", and the existing analyze ignore entries (pinned to the old groupId) no longer match.

This PR updates the groupId at every declaration and in the three analyze ignore entries, which is the change the upstream migration asks consumers to make. Artemis keeps full package & code compatibility across the move, so there are no Java/API changes — only Maven coordinates.

Security

This upgrade also fixes CVE-2026-27446 (CWE-306, missing authentication for a critical function — CVSS 9.8). An unauthenticated client using the Core protocol could force the broker to open an outbound federation connection to a rogue broker, enabling message injection/exfiltration. It affects Artemis 2.11.0–2.44.0 and is fixed in 2.52.0. Exposure here is limited because the broker is embedded, but the fix is worth having.

Notes on 2.54.0 release changes

The breaking items in the 2.50→2.54 notes don't apply to our embedded usage: Docker image path change, deprecated (non-functional) HTTP transport params, deprecated addSecuritySettings management methods, and default broker.xml security-setting clarifications.

Testing

  • dependency:analyze on dhis-support-artemis passes (the failure Dependabot's bump hit).
  • Dependency tree confirms all Artemis artifacts resolve to org.apache.artemis:*:2.54.0 and all Netty artifacts stay aligned at 4.2.13.Final.

🤖 Generated with Claude Code

…d to org.apache.artemis

Artemis moved to its own Apache top-level project and migrated its Maven
groupId from org.apache.activemq to org.apache.artemis as of 2.50.0. The
old coordinates are now relocation stubs, so bumping the version alone makes
dependency:analyze fail (declared org.apache.activemq:* vs resolved
org.apache.artemis:*). This updates the groupId at all declarations and the
analyze ignore entries.

Also fixes CVE-2026-27446 (missing authentication in Core protocol
federation), which affects Artemis 2.11.0-2.44.0 and is fixed in 2.52.0.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@sonarqubecloud
Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants