[ 
https://issues.apache.org/jira/browse/MNG-6967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17228168#comment-17228168
 ] 

Hudson commented on MNG-6967:
-----------------------------

Build succeeded in Jenkins: Maven » Maven TLP » maven » MNG-6169/MNG-6556 #14

See 
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6169%252FMNG-6556/14/

> Improve the command line output from maven-artifact
> ---------------------------------------------------
>
>                 Key: MNG-6967
>                 URL: https://issues.apache.org/jira/browse/MNG-6967
>             Project: Maven
>          Issue Type: Improvement
>          Components: Artifacts and Repositories
>    Affects Versions: 3.6.3
>            Reporter: Dennis Lundberg
>            Assignee: Dennis Lundberg
>            Priority: Major
>             Fix For: 3.7.0
>
>
> As is documented here
> https://maven.apache.org/pom.html#version-order-testing
> you can use the maven-artifact JAR file to test version numbers and their 
> relative order.
> Unfortunately the output does not match what is used in
> https://maven.apache.org/pom.html#version-order-specification
> when describing the "Trimming Examples". It's matter of {{==}} versus {{->}}. 
> I prefer the one used in the documentation, so I'd like to change 
> maven-artifact to use {{->}}. It respresents a transformation (trimming in 
> this case) -- not a an equality test.
> Another problem is that it does not show you the list of tokens that are the 
> result of parsing the version numbers. This can be quite useful when trying 
> to figure out why you are getting the results you are.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to