aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephan Siano (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ARIES-1103) esa-maven-plugin breaks maven 3 snapshot dependencies in subsystem manifest
Date Mon, 26 Aug 2013 10:37:53 GMT

     [ https://issues.apache.org/jira/browse/ARIES-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Stephan Siano updated ARIES-1103:
---------------------------------

    Description: 
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).

  was:
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.

    
> 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
>         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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message