On Wed, Dec 3, 2008 at 11:36 AM, Jukka Zitting <[EMAIL PROTECTED]> wrote: > Is this a problem? If yes, then we could keep such upstream > dependencies with the core for now, only moving those components that > aren't really related to changes in core components. That would leave > us with: > > * jackrabbit-jcr-tests > * jackrabbit-jcr-benchmark > * jackrabbit-jcr-rmi > * jackrabbit-jcr-servlet > * jackrabbit-classloader > * jackrabbit-ocm > * jackrabbit-ocm-nodemanagement
Well, I guess jcr-commons should really be part of the commons subproject, as it is supposed to help with the jcr api in general. And nothing could hinder us from using a snapshot dependency on jcr-commons in the trunk of core - we only have to take care and release jcr-commons before a new core release. Regards, Alex -- Alexander Klimetschek [EMAIL PROTECTED]
