[
https://issues.apache.org/jira/browse/FELIX-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stuart McCulloch closed FELIX-1886.
-----------------------------------
Resolution: Not A Problem
Closing as the bundleplugin now follows the rules documented at
http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html
> Bundle-SymbolicName generated with maven-bundle-plugin 2.0.0 is not the same
> as with 1.4.3
> ------------------------------------------------------------------------------------------
>
> Key: FELIX-1886
> URL: https://issues.apache.org/jira/browse/FELIX-1886
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-2.0.0
> Reporter: Bertrand Delacretaz
>
> I have noticed this with the jackrabbit-jcr-commons 2.0-beta3 module.
> 1) Build as is, uses maven-bundle-plugin 2.0.0, resulting MANIFEST.MF
> contains:
> Tool: Bnd-0.0.311
> Bundle-SymbolicName: org.apache.jackrabbit.jcr-commons
> (not sure if the version of bnd makes a difference)
> 2) Modify pom.xml to use maven-bundle-plugin 1.4.3, rebuild, resulting
> MANIFEST.MF contains:
> Tool: Bnd-0.0.255
> Bundle-SymbolicName: org.apache.jackrabbit.jackrabbit-jcr-commons
> The new symbolic name looks nicer, but the change is surprising - that
> should be documented (did I miss that?), and having a way to use the old
> Bundle-SymbolicName generation rules might be good.
> [1]
> http://svn.apache.org/repos/asf/jackrabbit/tags/2.0-beta3/jackrabbit-jcr-commons/
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
