Skip to content

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

Open
stian-sandvold wants to merge 1 commit into
2.43from
artemis-groupid-2.43
Open

chore(deps): bump artemis-jakarta 2.42.0 → 2.54.0 and migrate groupId to org.apache.artemis#24101
stian-sandvold wants to merge 1 commit into
2.43from
artemis-groupid-2.43

Conversation

@stian-sandvold

Copy link
Copy Markdown
Contributor

What

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

This ports the same fix already merged on the 2.42 branch (#24049) to the 2.43 branch. There is no open Dependabot Artemis PR on this branch; the bump and the groupId move are coupled (the new groupId only exists for Artemis ≥ 2.50), so they are done together here.

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 a 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.

Netty alignment

This branch carries the netty-bom import (added in 24048), so the larger Netty tree pulled in by Artemis ≥ 2.50 stays aligned at 4.2.13.Final — no class-skew.

Notes on 2.54.0 release changes

The breaking items in the 2.50→2.54 notes do not 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 a version-only bump hits).
  • 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

… to org.apache.artemis

Ports the fix from #24049 (2.42) to 2.43. Bumps artemis-jakarta.version
and migrates the Maven groupId org.apache.activemq → org.apache.artemis
(relocated as of Artemis 2.50.0, Apache TLP migration). Fixes CRITICAL
CVE-2026-27446 (missing-auth Core federation; affects 2.11.0–2.44.0,
fixed 2.52.0). Netty stays aligned at 4.2.13.Final via the netty-bom
import (#24048).
@stian-sandvold stian-sandvold requested a review from a team as a code owner June 2, 2026 18:34
@sonarqubecloud

sonarqubecloud Bot commented Jun 2, 2026

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.

1 participant