The spec also seems to not define the comparison output for when two tokens
have the same prefix, but one token is a qualifier, and the other is an
integer:
For such cases, the ComparableVersion code behaves oddly, in that it
outputs:
java -jar maven-artifact-3.5.3.jar 2 2.a
Display parameters
Sorry, the 1-0-2 == 1-2 induced me to read the < as a >.
The code is buggy because it produces a canonical form & a comparison
result that are inconsistent.
The canonical form is consistent with the spec (as I read the spec; if you
read it otherwise, please let me know).
Everything should be
Hi,
I am currently cleaning up the build of the Apache PLC4X project.
We are using Asciidoctor and a lot of its plugins to generate our site. We
always had to sort of double-run asciidoctor as when running as site plugin the
generated content is always generated into the root project.
Therefore
Hi to all,
we appreciate to announce the new release of Plexus Interpolation
Version 1.25.
https://codehaus-plexus.github.io/plexus-interpolation/
The list of fixed issues can be seen via the following link:
https://github.com/codehaus-plexus/plexus-interpolation/milestone/1?closed=1
Kind
no, current implementation result is 1-0-2 < 1-1
here is the proof:
$ java -jar maven-artifact-3.5.3.jar 1-0-2 1-1
Display parameters as parsed by Maven (in canonical form) and comparison result:
1. 1-0-2 == 1-2
1-0-2 < 1-1
2. 1-1 == 1-1
then explanations: who uses dashes (-) instead of dots
+1
Regards,
Hervé
Le mardi 29 mai 2018, 21:47:41 CEST Andreas Dangel a écrit :
> Hi,
>
> We solved 10 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12342689
> eName=Text=12317621
> There are still a couple of issues left in JIRA:
>
