Add pre bundled jars with different symbolic name about p2-maven-plugin

[tombujok]

So you would like to be able to edit the Manifest.MF file of an artifact that's already a bundle without using the 'override' option - basically without bundling it once more using BND? Do I get it correctly?

What do you mean by the "bnd prevent instruction"?

[nachtgold]

Yes, I want to change only the file name and the bundle symbolic name manifest element.

Like

<artifact>
     <id>org.apache.log4j:com.springsource.org.apache.log4j:1.2.16</id>
     <transitive>false</transitive>
     <bundled>true</bundled>
     <instructions>
        <Bundle-SymbolicName>org.apache.log4j</Bundle-SymbolicName>
     </instructions>
</artifact> 

This "bundled" setting prevent the normal BND bundle process and only the specified instructions will be executed (like changing the manifest imports or exports).

[tombujok]

The 'bundled' switch is not a good idea since there is already the 'override' switch.
It would have to be then:
override -> bundle
override -> manifest

I just do not get the business case why you would like to rename the bundles...
Forgeting p2 and OSGi - you cannot add a dependency in the pure maven renaming it at the same time...

[nachtgold]

My case is: I need org.apache.log4j:1.2.16 as dependency and spring source already offers a bundle (in their maven repo). But I do not find this bundle in a public P2 repo (only v1.2.15), so I want to host it myself.

[nachtgold]

I found https://svn.apache.org/repos/asf/logging/log4j/tags/v1_2_16/pom.xml so I use the same BND instructions and the result matches.

[tombujok]

Perfect. Thanks

[nachtgold]

Wow, if the BSN in the manifest already is correct, then your plugin changes the file name correctly. This saves a lot of work.

Sample: http://repo1.maven.org/maven2/net/java/dev/glazedlists/glazedlists_java15/1.8.0/glazedlists_java15-1.8.0.jar

groupId and artifactId are useless, but so I have to do anything. Thx 👍