Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong usage of Milestone Release Qualifier for jakarta.inject-api artifact #36

Open
laeubi opened this issue Aug 14, 2024 · 0 comments
Open

Comments

@laeubi
Copy link

laeubi commented Aug 14, 2024

There was a (at least assumed from the name) milestone release here with version 2.0.1.MR and even though central reports a new version as 2.0.1 this is actually wrong.

According to the Version Order Specification MR is treated as a plain qualifier and therefore higher than 2.0.1, to be correctly recognized as a milestone release it is only allowed to have a singe character immediately followed by a number like M1, M2, ... as it is correctly done for RC releases already.

grafik

Sadly this can't be fixed by now but should be avoided in new releases as it might confuse automatic tools that try to suggest new versions. Even though it looks like released on the same day one can see that there are already 93 references to this "false" artifact.

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

No branches or pull requests

1 participant