Thanks for replies! Yes, the super bundle approach (putting *all* neo modules and *all* their dependencies in one bundle) works in principle. But to be a deployable solution ... 1) it must exist in the Maven repo and be on a par with the Neo4j release 2) A configuration mechanism is required to choose the modules actually needed
To abandon the super bundle approach and as long as the original problem (Java Service Loader and OSGi) is not solved: how about bringing back the old-style (serviceloader-less) indexing API as an *alternate* entry point? This would allow thousands of OSGi users to use Neo4j > 1.2 and they would love it. Cheers, Jörg On Jul 20, 2011, at 9:20, Peter Neubauer wrote: > Could you please try the OSGi neo4j super bundle built in github / neo4j / > Neo4j - osgi / bundle? > > Fine grained bundle deployment interferes with the java service loader which > only looks in its own classpath. _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
