Hi, >c) Ship the jackrabbit deployment packages without Lucene integration >for Oak. This would allow people to start playing with Oak in their >existing deployments, but require some deployment changes for full Oak >functionality.
+1 I think this could be a way ... >f) Adjust the Jackrabbit deployment packages to use an embedded OSGi >container, and use it to selectively deploy the required >implementation components, including the correct version of Lucene. As we use jackrabbit as a JCA Adapter I don't know if this could be a problem ... >g) Or as a last resort, abandon the idea of a joint deployment >package. Jackrabbit Classic and Oak would be shipped in separate >deployment artifacts. Hmm I would like to see only one jackrabbit. Jackrabbit 3.0 should be the next step forward and users should not care about which kernel is inside or not. It would be great if there are steps described to upgrade or the upgrade process comes out of the box. greets claus
