maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Bentmann (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MNG-3526) Small change to artifact version parsing.
Date Sun, 07 Nov 2010 22:55:03 GMT

    [ http://jira.codehaus.org/browse/MNG-3526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=242351#action_242351
] 

Benjamin Bentmann commented on MNG-3526:
----------------------------------------

Should be possible to fix {{toString()}} by just using {{comparable.toString()}} instead of
trying to reconstruct the string from the parsed bits.

> Small change to artifact version parsing.
> -----------------------------------------
>
>                 Key: MNG-3526
>                 URL: http://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.1
>
>         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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message