Oh, right.
Only the bundles that org.neo4j:neo4j depends on exports packages. I
guess org.neo4j:neo4j
would have to re-export the packages it depends on, so that your application
can depend on org.neo4j:neo4j and use those packages. Is that the
appropriate way? I have little OSGi experience
Hi,
I'll try this later on and I'll keep you informed.
Also, you could use the maven-bundle-plugin which helps in managing bundle
creation and dependencies stuffs.
Nicolas.
Le 12 mars 2011 à 09:13, Tobias Ivarsson a écrit :
Oh, right.
Only the bundles that org.neo4j:neo4j depends on
Hi Nicolas,
We should be using the maven-bundle-plugin on the individual components, but
I'll have to check to make sure that they look right. The org.neo4j:neo4j
artifact is just a dependency jar, so it doesn't itself have anything to
export. That's why Tobias suggested grabbing the
Ok,
This works fine when using directly bundles which export packages.
Thx
Le 12 mars 2011 à 09:13, Tobias Ivarsson a écrit :
Oh, right.
Only the bundles that org.neo4j:neo4j depends on exports packages. I
guess org.neo4j:neo4j
would have to re-export the packages it depends on, so that
Hi,
I'm planning to use Neo4j under OSGi framework. Because org.neo4j:neo4j defines
the needed headers (in MANIFEST.MF), it can be deployed as a bundle on equinox
or felix.
Unfortunatelly, the bundle doesn't export any package so it's quite unuseful
for me as my own bundle can't import them.
I
5 matches
Mail list logo