commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting" <>
Subject Federated commons and JCR
Date Thu, 18 Dec 2008 14:04:26 GMT

In the Jackrabbit project we're thinking about setting up a "JCR
Commons" subproject for some of our generic JCR tools that are not
tightly coupled to the Jackrabbit content repository. See [1] for more

It was suggested that we consider bringing those components to Apache
Commons, but I'm not too excited about the idea at least for now. The
Jackrabbit community had concerns about even a separate mailing list for the proposed subproject, and
bringing the components to a separate TLP would cause an even greater
split in our development efforts and community. (And quite frankly I
find the dev@commons list really hard to keep track of without
elaborate filtering rules.)

I'd be more interested in pursuing Henri's recent idea on "federated
commons" (see [2]). We'd for now keep the JCR Commons components in
Jackrabbit, but could adopt some quality, branding, and release
practices from Apache Commons (details to be worked out). Would this
be a good idea?



Jukka Zitting

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message