[jira] Commented: (MECLIPSE-385) version normalization from Maven to Eclipse is incorrect in some corner cases

["Carlos Sanchez (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MECLIPSE-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_122303 ] 

Carlos Sanchez commented on MECLIPSE-385:
-----------------------------------------

That goal has been deprecated, please look into http://felix.apache.org/site/maven-bundle-plugin-bnd.html "Adding OSGi metadata to existing projects without changing the packaging type"


> 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-EclipseOSGiManifestWriterTest.txt, 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