[
http://jira.codehaus.org/browse/MSHARED-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=212823#action_212823
]
luke w patterson commented on MSHARED-98:
-----------------------------------------
saw something that might be related, throwing this out there so there's a trail:
"Fix inconsistent maven->osgi version conversion between maven-bundle-plugin
and DefaultMaven2OsgiConverter"
https://issues.apache.org/jira/browse/FELIX-2173
> Maven2OsgiConverter unnecessarily pads version numbers
> ------------------------------------------------------
>
> Key: MSHARED-98
> URL: http://jira.codehaus.org/browse/MSHARED-98
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-osgi
> Reporter: Matthew Beermann
> Attachments: MSHARED-98-maven-osgi.patch, MSHARED-98-maven-osgi.patch
>
>
> In DefaultMavenOsgiConverter#getVersion(), there's logic to the effect of:
> /* convert
> * 1.string -> 1.0.0.string
> * 1.2.string -> 1.2.0.string
> * 1 -> 1.0.0
> * 1.1 -> 1.1.0
> */
> ...which is unnecessary; the version number only needs to be padded out to
> three places when there's a qualifier present.
--
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
