Jukka Zitting wrote:
* jackrabbit-jcr-tests: Some fixes now and then ... I would make this
a separate cluster
Quite a few actually, jcr-tests is one of our more actively developed
components.
Architecturally it would warrant it's own subproject (like JCRTCK),
but I pooled it in the core project to keep the number of subprojects
manageable. There is also little end-user demand for jcr-tests.
But yes, if we want to split down the core JCR subproject, I would
first go with JCRTCK and only after that start considering any other
splittings.
+1, as JSR-283 approaches and more people start to implement it, the
need for a cleanly separate JIRA project to track spec/TCK-related
problems will increase.
Florent
--
Florent Guillaume, Director of R&D, Nuxeo
Open Source Enterprise Content Management (ECM)
http://www.nuxeo.com http://www.nuxeo.org +33 1 40 33 79 87
