As the Import-Package header generated for you bundle has a an entry
for 'com.jamesmurty.utils' package it needs to be provided by some
bundle. Now either your code actually requires it or its an optional
dependency of one of the jar you have embedded. if its the former case
then have a bundle for
Ah... This might be a solution:
!.,org.osgi.framework,*
Note that I've added "!.," to the start of the value to ignore the project dir.
However, I now have another problem with an unresolved dependency that may have
appeared as a consequence of this change:
$ java -jar bin/felix.jar
ER
Hi Tom,
Looking at the Felix ManifestParser [1] it complains because your
Import-Package instruction has a Dot '.' in it which is invalid. I am
not sure why bnd/maven-bundle-plugin generates such an instruction.
One possible reason is provided at [2] which says that it might be
because you compila
Hi,
I am new to OSGi and Maven. I am using the maven-bundle-plugin to bundle my
project (embedding it's dependencies) as follows:
org.apache.felix
maven-bundle-plugin
1.4.0
4 matches
Mail list logo