In the Apache Jackrabbit project we've decided to create a new JCR Commons subproject for developing and managing the set of generic JCR tools that has grown over time around the core Jackrabbit content repository implementation.
The JCR Commons subproject will to some extent resemble the Apache Commons project, and I'm hoping to use some of the ideas put forward by Henri in his blog post about a "federated commons".
I'm hoping to flesh out the details of this new subproject over the next month or two. It would be nice to have releases of all the new JCR Commons components ready to be used as dependencies for the upcoming Jackrabbit 1.6 release.
Thanks Jukka for reading the rambling post way back when, and for acting upon it! :)ReplyDelete
The simplest step I'd like to see is for JCR Commons to have two groups with svn rw karma - jackrabbit's group and commons' group. It'd rock to have you being a child of our maven pom, and I'd like to see you guys hooked in from our site as Apache Commons components (hosted at JackRabbit).
I'm asking more than I'm giving - but figured I'd bid high ;) Really I don't have any solid ideas for how to implement the federated commons, but I think you get the general gist. Have the commons components, but have them live inside your community instead of creating commons communities whose focus is small components without the original context.
Let me know how I can help.