You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Marshall Schor (JIRA)" <ji...@codehaus.org> on 2008/02/04 18:24:57 UTC
[jira] Updated: (MECLIPSE-385) version normalization from Maven to
Eclipse is incorrect in some corner cases
[ http://jira.codehaus.org/browse/MECLIPSE-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor updated MECLIPSE-385:
------------------------------------
Attachment: patch-getNormalizedVersion.txt
I grant these patches under the Apache 2.0 license.
> version normalization from Maven to Eclipse is incorrect in some corner cases
> -----------------------------------------------------------------------------
>
> Key: MECLIPSE-385
> URL: http://jira.codehaus.org/browse/MECLIPSE-385
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: OSGi, Manifest, PDE support
> Reporter: Marshall Schor
> Priority: Minor
> Attachments: patch-getNormalizedVersion.txt
>
>
> The code in EclipseOSGiManifestWriter.getNormalizedVersion is incorrect in the case where there are 4 components as input to the version. For instance, it converts 2.3.0.incubating-SNAPSHOT to 2.3.0.incubating.SNAPSHOT - this has 5 components, separated by "periods" and is invalid as an Eclipse version number; Eclipse version numbers have 4 components (maximum) where the first 3 are numeric. See http://help.eclipse.org/stable/index.jsp?topic=/org.eclipse.pde.doc.user/guide/tasks/pde_version_qualifiers.htm
--
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