You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Paul Gier (JIRA)" <ji...@codehaus.org> on 2008/04/16 00:21:58 UTC
[jira] Created: (MNG-3526) Small change to artifact version
parsing.
Small change to artifact version parsing.
-----------------------------------------
Key: MNG-3526
URL: http://jira.codehaus.org/browse/MNG-3526
Project: Maven 2
Issue Type: Improvement
Components: General
Affects Versions: 2.0.9
Reporter: Paul Gier
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
[jira] Commented: (MNG-3526) Small change to artifact version
parsing.
Posted by "Herve Boutemy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=132714#action_132714 ]
Herve Boutemy commented on MNG-3526:
------------------------------------
the idea seems interesting, but this change breaks toString() result:
{code}new DefaultArtifactVersion( "1.0.1.beta1" ).toString() -> "1.0.1-beta1"{code}
> Small change to artifact version parsing.
> -----------------------------------------
>
> Key: MNG-3526
> URL: http://jira.codehaus.org/browse/MNG-3526
> Project: Maven 2
> Issue Type: Improvement
> Components: General
> Affects Versions: 2.0.9
> Reporter: Paul Gier
> 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
[jira] Commented: (MNG-3526) Small change to artifact version
parsing.
Posted by "Herve Boutemy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131513#action_131513 ]
Herve Boutemy commented on MNG-3526:
------------------------------------
see http://docs.codehaus.org/display/MAVEN/Versioning
> Small change to artifact version parsing.
> -----------------------------------------
>
> Key: MNG-3526
> URL: http://jira.codehaus.org/browse/MNG-3526
> Project: Maven 2
> Issue Type: Improvement
> Components: General
> Affects Versions: 2.0.9
> Reporter: Paul Gier
> 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
[jira] Updated: (MNG-3526) Small change to artifact version
parsing.
Posted by "Paul Gier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Gier updated MNG-3526:
---------------------------
Attachment: MNG-3526-maven-artifact-r648413.patch
Attaching a patch with the change to the DefaultArtifactVersion, and updates to the unit tests.
> Small change to artifact version parsing.
> -----------------------------------------
>
> Key: MNG-3526
> URL: http://jira.codehaus.org/browse/MNG-3526
> Project: Maven 2
> Issue Type: Improvement
> Components: General
> Affects Versions: 2.0.9
> Reporter: Paul Gier
> 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
[jira] Updated: (MNG-3526) Small change to artifact version
parsing.
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-3526:
------------------------------
Fix Version/s: (was: 2.2.x (to be reviewed))
3.1
> 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
[jira] Commented: (MNG-3526) Small change to artifact version
parsing.
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Updated: (MNG-3526) Small change to artifact version
parsing.
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-3526:
------------------------------
Fix Version/s: 2.0.x
> Small change to artifact version parsing.
> -----------------------------------------
>
> Key: MNG-3526
> URL: http://jira.codehaus.org/browse/MNG-3526
> Project: Maven 2
> Issue Type: Improvement
> Components: General
> Affects Versions: 2.0.9
> Reporter: Paul Gier
> Fix For: 2.0.x
>
> 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