Publish JUnit 5 compatibility coordinates as Maven relocations#1280
Open
baev wants to merge 1 commit into
Open
Publish JUnit 5 compatibility coordinates as Maven relocations#1280baev wants to merge 1 commit into
baev wants to merge 1 commit into
Conversation
baev
added
type:bug
pratushnyi
approved these changes
May 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
The deprecated JUnit 5 coordinates now publish as relocation POMs to the renamed Jupiter artifacts. Existing builds that still reference
io.qameta.allure:allure-junit5orio.qameta.allure:allure-junit5-assertcan continue their migration path towardallure-jupiterandallure-jupiter-assert, while new setups are clearly guided to the canonical artifact names.The release checks now verify that both primary and legacy coordinates generate the expected POM metadata, including relocation details, so publishing catches this compatibility path before artifacts reach users. Documentation has also been updated to describe the old coordinates as deprecated relocations instead of aliases.
The change should fix the recent publish failure #1279
Checklist