You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Stephen Connolly (JIRA)" <ji...@codehaus.org> on 2014/01/06 10:41:45 UTC
[jira] (MNG-3526) Small change to artifact version parsing.
[ https://jira.codehaus.org/browse/MNG-3526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=338104#comment-338104 ]
Stephen Connolly commented on MNG-3526:
---------------------------------------
All integration tests pass: https://builds.apache.org/job/core-integration-testing-maven-3-jdk-1.7/928/
> Small change to artifact version parsing.
> -----------------------------------------
>
> Key: MNG-3526
> URL: https://jira.codehaus.org/browse/MNG-3526
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: General
> Affects Versions: 2.0.9
> Reporter: Paul Gier
> Fix For: 3.2
>
> Attachments: MNG-3526-maven-artifact-r648413.patch
>
>
> We currently many projects that use an OSGi compatible scheme for release version numbers. The OSGi spec does not currently allow a "-" to determine the location of the qualifier. So instead of the maven standard like this:
> 1.0.1-beta-1
> We have something like this:
> 1.0.1.beta1
> Maven's currently handles this by treating the entire version string as a classifier. It would be helpful this could be parsed as
> major = 1
> minor = 0
> incremental = 1
> qualifier = beta1
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira