Re: Resolving a type from a wrapped jar file

2018-09-09 Thread Jean-Baptiste Onofré
Hi, Instead of importing packages, you can embed the packages in your bundle. You have three ways to achieve this using the maven-bundle-plugin: 1. Using Bundle-Classpath instruction 2. Using Embed-Dependency instruction 3. Using Private-Package instruction Regards JB On 09/09/2018 21:35,

Re: Resolving a type from a wrapped jar file

2018-09-09 Thread David Jencks
Hi David, Bundle-ClassPath is an osgi header that specifies the internal class path structure of a bundle. -conditionalpackage is a bnd instruction that pulls in specific packages that are actually used from dependencies. I was suggesting including all of neo4j in the bundle using the

Re: Resolving a type from a wrapped jar file

2018-09-09 Thread David Leangen
Thanks for this info. Could you please explain more what you mean by: > uses bundle-classpath Is this something different from Conditional-Package? Cheers, =David > On Sep 10, 2018, at 6:31, David Jencks wrote: > > IANAL and I really can’t understand the GPLv3. > > rebundling or

Re: Resolving a type from a wrapped jar file

2018-09-09 Thread David Jencks
IANAL and I really can’t understand the GPLv3. rebundling or wrapping neo4j jars definitely modifies them. I’m not sure if having karaf or maven do this on the user’s system compared with distributing such already modified jars makes a difference to the license implications. If you make a jar

Re: Resolving a type from a wrapped jar file

2018-09-09 Thread Steinar Bang
> Jean-Baptiste Onofré : > why you don't just put this as private package. You will avoid class > loading issue this way. > In OSGi, not all is necessary an import. It could be a private package > and/or embed dependency. It means the packages are embedded in the > bundle. The bundle is

Re: Resolving a type from a wrapped jar file

2018-09-09 Thread Jean-Baptiste Onofré
Hi, why you don't just put this as private package. You will avoid class loading issue this way. In OSGi, not all is necessary an import. It could be a private package and/or embed dependency. It means the packages are embedded in the bundle. The bundle is "fat" but you avoid classloading issue

Re: Resolving a type from a wrapped jar file

2018-09-09 Thread Steinar Bang
> Steinar Bang : > My bundle, ie. the bundle containing the failing component, contains an > import-package for org.neo4j.graphdb. > But the bundle where the error occurs, ie. > wrap_file__home_sb_.m2_repository_org_neo4j_neo4j-graphdb-api_3.4.7_neo4j-graphdb-api-3.4.7.jar > does *not*

Re: Resolving a type from a wrapped jar file

2018-09-09 Thread Steinar Bang
>>>>> Steinar Bang : > The next problem is problem resolving a type from a wrapped jar file > when activating the component: > 2018-09-09T16:36:41,324 | ERROR | Thread-97| karaf > | 56 - no.priv.bang.neo4j.karaf - 1.0.0.SNAPSHOT |

Resolving a type from a wrapped jar file (Was: Problems accessing SystemMBean from a DS component)

2018-09-09 Thread Steinar Bang
lem is problem resolving a type from a wrapped jar file when activating the component: 2018-09-09T16:36:41,324 | ERROR | Thread-97| karaf | 56 - no.priv.bang.neo4j.karaf - 1.0.0.SNAPSHOT | BundleComponentActivator : Bundle [56] Unexpected failure en