how to use maven bundle plugin to exclude package out of bundle
osgi,pom.xml,exclude,maven-bundle-plugin
I have made it works. Basically, we need to use a combination between and . Tell maven bundle plugin to not export this package and this package is not a private package --> that means we dont need to keep this package in the bundle <Export-Package>!com.xxx.yyyy.common</Export-Package> <Private-Package>!com.xxx.yyyy.common</Private-Package> ...
src is used instead of target for bundling package
osgi,osgi-bundle,maven-bundle-plugin
Following Link explains how to include resources in the final bundle under topic "Instructions -> Include Resource". http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html Following the documentation, I added Included-Resource tag in instructions in pom xml as below and it worked i.e. the plugin packed the resource file from target folder. <instructions> <Include-Resource> META-INF/persistence.properties=target/classes/META-INF/persistence.properties </Include-Resource>...
Maven/Removing timestamps from build
java,maven-3,maven-bundle-plugin
I have the same problem I just found the answer to the header problem on google. I realise this is a year or so late for you. <plugin> <groupId>org.apache.felix</groupId> <artifactId>maven-bundle-plugin</artifactId> <configuration> <archive> <addMavenDescriptor>false</addMavenDescriptor> </archive> <instructions> <_removeheaders>Bnd-LastModified</_removeheaders> ...
Pack ServletContainerInitializers from different bundles to a single OSGi bundle
maven,tomcat,osgi,maven-bundle-plugin
I found the answer for this. You can use maven-shade-plugin for this. e.g. In My scenario I can pack both SCIs as follows <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-shade-plugin</artifactId> <version>2.3</version> <executions> <execution> <phase>package</phase> <goals> <goal>shade</goal> </goals> <configuration> <transformers> <transformer...
When using “bundle” packaging with maven-bundle-plugin goals are executed twice
java,maven,maven-bundle-plugin
I recall us having a similar problem (specifically, the bundle was deployed twice) when we upgraded maven-bundle-plugin to 2.5.4. We downgraded it to 2.5.3 to solve our problems. I have not dug deeper to see if this is a bug or if there are just other requirements for configuration for...