jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Klimetschek" <aklim...@day.com>
Subject Re: Apache JCR Commons
Date Wed, 03 Dec 2008 10:45:25 GMT
On Wed, Dec 3, 2008 at 11:36 AM, Jukka Zitting <jukka.zitting@gmail.com> 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
alexander.klimetschek@day.com

Mime
View raw message