Hi @Sb2512 ,
Try below solution:
1. Replace maven-bundle-plugin with bnd-maven-plugin
In your pom.xml:
<plugin>
<groupId>biz.aQute.bnd</groupId>
<artifactId>bnd-maven-plugin</artifactId>
<version>6.4.0</version> <!-- or latest -->
<executions>
<execution>
<goals>
<goal>bnd-process</goal>
</goals>
</execution>
</executions>
</plugin>
2. Add bnd.bnd file in the same module (typically under /core)
Create a bnd.bnd file (in the same directory as your pom.xml) with the following content:
Bundle-Name: My Bundle
Bundle-SymbolicName: com.mycompany.core
Bundle-Version: 1.0.0
# Import Packages
Import-Package: \
!org.codehaus.groovy.*,\
javax.inject;version=0.0.0,\
javax.annotation;version=0.0.0,\
!org.bouncycastle.*,\
!javax.cache.*,\
*
# Export Packages
Export-Package: \
com.akamai.edgegrid.signer.*
# Embedded Dependencies (include-dependency is bnd syntax)
-includeresource: \
@flying-saucer-core.jar,\
@flying-saucer-pdf.jar,\
@jsoup.jar,\
@javaslang.jar,\
@javaslang-jackson.jar
# Make sure they are included from dependencies
-runbundles: \
flying-saucer-core,\
flying-saucer-pdf,\
jsoup,\
javaslang,\
javaslang-jackson
3. Add the dependencies in pom.xml
Make sure the JARs to embed are added as dependencies with scope=compile:
<dependencies>
<dependency>
<groupId>org.jsoup</groupId>
<artifactId>jsoup</artifactId>
<version>1.13.1</version>
</dependency>
<dependency>
<groupId>org.xhtmlrenderer</groupId>
<artifactId>flying-saucer-core</artifactId>
<version>9.1.20</version>
</dependency>
<dependency>
<groupId>org.xhtmlrenderer</groupId>
<artifactId>flying-saucer-pdf</artifactId>
<version>9.1.20</version>
</dependency>
<dependency>
<groupId>io.vavr</groupId>
<artifactId>vavr</artifactId>
<version>0.10.3</version>
</dependency>
<dependency>
<groupId>io.vavr</groupId>
<artifactId>vavr-jackson</artifactId>
<version>0.10.3</version>
</dependency>
</dependencies>
4. Embed JARs in the OSGi bundle using bnd-maven-plugin
Ensure the bnd.bnd file points to where the dependencies are built (they must be in your local Maven repo or project build path).
You can also use -buildpath or configure -includeresource with ${@} to automate:
-includeresource: @${@}
But most commonly, just use @jar-name.jar or Maven coordinates if scripting with BND workspace.
Build your bundle:
mvn clean install
Then use:
unzip -l target/yourbundle.jar
You’ll see embedded JARs inside the bundle, and exports will reflect only what you declared.
Note:
Don't forget to remove maven-bundle-plugin from the old pom.xml.
The bnd.bnd file must reside in the same module as the bundle you're building.
The dependencies are pulled from the build path, so Maven must resolve them correctly.
Regards,
Amit
