Sub-bundles: -buildpath vs. -classpath

GENERAL
1

Hi Peter @pkriens , I am trying to following your hint to create a single wrapper bundle in my workspace using sub-bundles for each lib I want to wrap. (based on this)

I have the feeling -buildpath in a sub-bundle works different than in a normal bnd.bnd. In sub-bundle I had to use -classpath instead, to get same result.

Any pointers to why that is?

Here more details:

Before I had a separate wrapper bundle with a bnd.bnd and a -buildpath instruction:

-buildpath: \
	org.apache.poi:poi;version=latest,\

This basically extracted the dependency in my wrapper jar.

But in a sub-bundle mysubbundle.bnd the -buildpath seems to be ignored.
I could only get the same result as before when I use -classpath like this:

-classpath: \
	${repo;org.apache.poi:poi;latest},\

my parent bnd.bnd is simple like this:

-resourceonly: true
-sub: *.bnd
2

The -buildpath is a project instruction. This means that it must be placed in the bnd.bnd file, not in the sub bnd file. A project can only have a single -buildpath.

1 Like