[
https://issues.apache.org/jira/browse/ARIES-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor resolved ARIES-1103.
--------------------------------
Resolution: Fixed
Committed changes in revision 1590210 that should address it. Now, the version
(and the symbolic name) will be used from the bundle or subsystem manifest.
Also, appropriate "type" attribute will be added (if needed).
> esa-maven-plugin breaks maven 3 snapshot dependencies in subsystem manifest
> ---------------------------------------------------------------------------
>
> Key: ARIES-1103
> URL: https://issues.apache.org/jira/browse/ARIES-1103
> Project: Aries
> Issue Type: Bug
> Reporter: Stephan Siano
> Assignee: Jarek Gawor
> Attachments: versionnumber.diff
>
>
> With maven3 SNAPSHOT dependencies are stored as
> a-0.0.1-20101204.150527-6.jar, not as a-0.0.1-SNAPSHOT.jar if they are not
> built within the same reactor.
> Maven dependencies will be resolved fine, however the esa-maven-plugin will
> generate wrong subsystem manifests from this.
> The bundle-symbolic-name is parsed from the manifest
> (maven2OsgiConverter.getBundleSymbolicName(artifact) does that), but the
> version put into the artifact is generated with Analyzer.cleanupVersion(),
> which will generate a completely wrong qualifier (6) from the maven version
> number.
> I think the only way to get the correct version number is to parse it from
> the bundle's manifest (as it is done for the bundle symbolic name).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
