Hi all, Well then, in the meantime I managed to modify the Jackrabbit libraries to be valid OSGi bundles. So we will probably in the near future remove the respective bundle inclusions again and just add the jackrabbit-jcr-commons bundle to the list of bundles to be installed.
Regards Felix Am Donnerstag, den 24.01.2008, 08:55 +0100 schrieb Felix Meschberger: > Hi all, > > Based on discussions in [1] and issue SLING-176 [2], I removed the > export of the jackrabbit-jcr-commons packages from the jcr/api bundle. I > thought, that this would only be a minor issue, but was completely > wrong: These packages are used throughout Sling in multiple projects, > which caused confusion as Sling did build but not run. Sorry for any > inconvenience. > > Yet, I am not happy with the current situation: There are far too many > hand-crafted inclusions of the jackrabbit-jcr-commons packages. To fix > the situation I see two possible solutions: > > (1) We create a new bundle jcr/base (or similar) which would export > jackrabbit-jcr-commons > and would also take the Session pooling functionality from the > jcr/api bundle. This > is the approached proposed by issue SLING-185. > > (2) Ask Jackrabbit to modify the jackrabbit-jcr-commons project to > make it an OSGi bundle. > This solution has the big advantage, that we may safely and > easily take over the > official released library from Jackrabbit and do not have to > create the bundling > outselves. > > The longer I think of it, the longer I like the second solution. WDYT ? > > Regards > Felix > > [1] http://markmail.org/message/q25llm4f5z4djrbl > [2] http://issues.apache.org/jira/browse/SLING-176 > [3] http://issues.apache.org/jira/browse/SLING-185
