Relocate arquillian-junit-5-* to arquillian-junit-jupiter and add JUnit 6.x testing

[rhusar]

Fix #805 and #808

Core design:

Rename artefactId and groupId to remove explicit 'junit5' reference.
Add relocation POM.
Does NOT rename packages.

Summary by Sourcery

Relocate the JUnit 5 integration to new arquillian-junit-jupiter artifacts and introduce infrastructure to verify compatibility with JUnit 6.

New Features:

• Add a JUnit 6 Maven profile that tests the JUnit Jupiter modules against JUnit 6 on Java 17 and 21.
• Introduce a relocations module providing compatibility artifacts for the old arquillian-junit5 coordinates.

Enhancements:

• Rename and repackage the existing JUnit 5 modules to arquillian-junit-jupiter-* and update references throughout the build and BOM.
• Clarify BOM dependency sections to distinguish JUnit 4.x, JUnit Jupiter, and the relocated JUnit 5.x artifacts.

CI:

• Extend the GitHub Actions CI pipeline with a job that runs the JUnit Jupiter modules under the JUnit 6 profile on supported JDKs.

[sourcery-ai]

Reviewer's Guide

Relocates the JUnit 5 integration to a new JUnit Jupiter module namespace, adds relocation POMs for backward compatibility, and introduces CI/build support for testing the JUnit Jupiter modules against both JUnit 5.x and 6.x (Java 17+).

Flow diagram for updated CI workflow with JUnit 6 verification

flowchart TD
  start[CI triggered] --> matrix_default

  subgraph job_default
    matrix_default[Job verify matrix java 8 11 17] --> checkout_default[Checkout arquillian-core]
    checkout_default --> setup_java_default[Setup JDK matrix.java]
    setup_java_default --> maven_verify_default[Maven clean verify]
  end

  start --> matrix_junit6

  subgraph job_junit6
    matrix_junit6[Job junit6-verify matrix java 17 21] --> checkout_junit6[Checkout arquillian-core]
    checkout_junit6 --> setup_java_junit6[Setup JDK matrix.java]
    setup_java_junit6 --> maven_verify_junit6[Maven clean verify with profile junit6 and modules junit-jupiter/core and junit-jupiter/container]
  end

Loading

File-Level Changes

Change	Details	Files
Introduce CI job to verify JUnit Jupiter modules against JUnit 6 on Java 17 and 21.	Add junit6-verify job to GitHub Actions workflow using a Java version matrix (17, 21). Run Maven with -Pjunit6 profile and restrict build to junit-jupiter/core and junit-jupiter/container modules with dependencies (-am).	.github/workflows/ci.yml
Rename and re-namespace JUnit 5 modules to JUnit Jupiter and update internal references.	Rename junit5 module directory and parent POM to junit-jupiter with new groupId org.jboss.arquillian.jupiter and artifactId arquillian-junit-jupiter-parent. Rename core and container submodule POMs to arquillian-junit-jupiter-* with updated groupId and artifactIds, and adjust module names to say "JUnit Jupiter". Update integration test POM to depend on the new arquillian-junit-jupiter-container artifact. Update root pom.xml to reference junit-jupiter module instead of junit5 and add new relocations aggregator module.	junit5/core/pom.xml junit5/container/pom.xml junit5/pom.xml junit5/README.adoc junit-jupiter/core/pom.xml junit-jupiter/container/pom.xml junit-jupiter/pom.xml junit-jupiter/README.adoc integration-tests/junit5-tests/pom.xml pom.xml
Adjust BOM and build configuration to differentiate JUnit 4.x, JUnit Jupiter, and the relocated JUnit 5.x artifacts, and to support JUnit 6 testing.	Clarify comments in BOM to label JUnit 4.x, JUnit Jupiter, and relocated JUnit 5.x dependencies. Add dependencies on the new arquillian-junit-jupiter-core and -container artifacts to the BOM. Rename version property from version.junit5 to version.junit-jupiter in build POM and use it for junit-bom import. Add junit6 Maven profile overriding version.junit-jupiter to 6.0.2 for testing with JUnit 6.	bom/pom.xml build/pom.xml
Add relocation POMs to preserve old org.jboss.arquillian.junit5 coordinates and point them to the new JUnit Jupiter artifacts.	Create relocations parent POM aggregating relocation modules for JUnit 5 core and container artifacts. Define relocations/arquillian-junit5-core POM that declares old coordinates and distributionManagement/relocation to arquillian-junit-jupiter-core, with dependency on the new artifact. Define relocations/arquillian-junit5-container POM similarly relocating to arquillian-junit-jupiter-container.	relocations/pom.xml relocations/arquillian-junit5-core/pom.xml relocations/arquillian-junit5-container/pom.xml

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#805	Rename the Arquillian JUnit 5 modules/artifacts from arquillian-junit5-* to arquillian-junit-jupiter-* across the project (modules, groupIds/artifactIds, and usages).	✅
#805	Provide Maven relocation POMs so the old org.jboss.arquillian.junit5:arquillian-junit5-* artifacts are relocated to the new org.jboss.arquillian.jupiter:arquillian-junit-jupiter-* artifacts.	✅

Possibly linked issues

• Add profile/workflow to verify junit 6 runtime compatibility #808: PR fulfills the requested Maven relocation from arquillian-junit5-* to arquillian-junit-jupiter and updates usages accordingly.
• #(unknown): PR adds JUnit 6.x test profile/workflow and provides the relocated JUnit Jupiter container artifacts requested.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[rhusar]

@jamezp please have a look

[sourcery-ai]

Hey - I've left some high level feedback:

• In the relocation POMs (relocations/arquillian-junit5-core and relocations/arquillian-junit5-container), consider changing the packaging to pom and removing the explicit dependency on the new junit-jupiter artifacts so that the relocated coordinates don’t introduce unnecessary transitive dependencies and rely purely on Maven’s relocation metadata.
• The relocation modules currently inherit from arquillian-build while the relocations parent POM inherits from arquillian-parent; it may be worth aligning these parents (or documenting the rationale) to keep the module hierarchy and build configuration consistent.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- In the relocation POMs (`relocations/arquillian-junit5-core` and `relocations/arquillian-junit5-container`), consider changing the packaging to `pom` and removing the explicit dependency on the new `junit-jupiter` artifacts so that the relocated coordinates don’t introduce unnecessary transitive dependencies and rely purely on Maven’s relocation metadata.
- The relocation modules currently inherit from `arquillian-build` while the relocations parent POM inherits from `arquillian-parent`; it may be worth aligning these parents (or documenting the rationale) to keep the module hierarchy and build configuration consistent.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[rhusar]

Hey - I've left some high level feedback:

• In the relocation POMs (relocations/arquillian-junit5-core and relocations/arquillian-junit5-container), consider changing the packaging to pom and removing the explicit dependency on the new junit-jupiter artifacts so that the relocated coordinates don’t introduce unnecessary transitive dependencies and rely purely on Maven’s relocation metadata.
• The relocation modules currently inherit from arquillian-build while the relocations parent POM inherits from arquillian-parent; it may be worth aligning these parents (or documenting the rationale) to keep the module hierarchy and build configuration consistent.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- In the relocation POMs (`relocations/arquillian-junit5-core` and `relocations/arquillian-junit5-container`), consider changing the packaging to `pom` and removing the explicit dependency on the new `junit-jupiter` artifacts so that the relocated coordinates don’t introduce unnecessary transitive dependencies and rely purely on Maven’s relocation metadata.
- The relocation modules currently inherit from `arquillian-build` while the relocations parent POM inherits from `arquillian-parent`; it may be worth aligning these parents (or documenting the rationale) to keep the module hierarchy and build configuration consistent.

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Addressed.

[hantsy]

I wish the Arquillian core adopting JUnit 6 would be in a new major release (e.g., 2.0), and the JDK baseline would be upgraded to Java 17+ (and all API/SPI code cleaned up to Java 17).