[
https://issues.apache.org/jira/browse/MRESOLVER-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17940636#comment-17940636
]
Tamas Cservenak commented on MRESOLVER-686:
-------------------------------------------
Refd issue contains two kind of "unorthodox" version numbers:
* '-SNAPSHOT' versions + AF
* with hex versions
Unsure what the problem was in first case, but in second according to version
spec as docd here
[https://github.com/apache/maven-resolver/blob/81e5a0ed635081c8797e02f394a836a3027b33b0/maven-resolver-util/src/main/java/org/eclipse/aether/util/version/package-info.java]
this result in a potentially long "segments" (as each transition from number
to letter and other way around denotes a segment boundary, see "implicit
delimiters". In short, Maven does not handle versions as "opaque strings" (it
cannot, as it has to define ordering), but hex versions is not something it can
use, at least not without some "orthodox" (read: sane) prefix like
"1.0.0-deadbeef" or alike.
> Exception: Comparison method violates its general contract
> ----------------------------------------------------------
>
> Key: MRESOLVER-686
> URL: https://issues.apache.org/jira/browse/MRESOLVER-686
> Project: Maven Resolver
> Issue Type: Bug
> Components: Resolver
> Reporter: Ralf Naujokat
> Priority: Minor
>
> I got this exception when using the versions-maven-plugin
> while scanning for dependency updates.
> it looks like the error doesn't come from the plugin but from some internal
> maven component.
> many details are already discussed here:
> [https://github.com/mojohaus/versions/issues/1147]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
