Hi, the classloader has been moved to the jackrabbit commons area. see http://markmail.org/message/qqlvlwpgi5oauak6
I think we didn't release it as part of 2.0 because no changes were necessary and it should basically work with a JCR 1.0 or 2.0 repository. what changes do you have in mind? would those changes add dependencies to sling modules? if there's more interest in the sling community to further develop the code then this is probably a good move. but then we shouldn't keep the code in jackrabbit commons. I'd rather have it in just one place. regards marcel On Mon, Jan 25, 2010 at 09:02, Carsten Ziegeler <[email protected]> wrote: > Hi, > > first, sorry for the crosspost :) > > I think we briefly discussed this topic some time ago: the Jackrabbit > 1.x versions provide a repository classloader which is not available > anymore in 2.0. > In Sling we provide a complete scripting framework based on top of the > repository and we're using the Jackrabbit classloader code and extended it. > > As Jackrabbit is not using the code anymore, but Sling is, I think it > makes perfectly sense to move/copy the code to Sling. > > So I would like to copy the classloader code into the Sling repo in the > next days and modifiy it to suit Sling's needs a little bit more. This > has no impact on Jackrabbit as 2.0 does not contain the code at all and > it still remains in the 1.x branch. > > Basically this is more a FYI as no legal steps etc are involved :) But > before doing this I want to be sure that there are zero objections. > > Regards > Carsten > -- > Carsten Ziegeler > [email protected] >
