You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
The text was updated successfully, but these errors were encountered:
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 as2.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.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.
The text was updated successfully, but these errors were encountered: