Hi,
On Thu, Dec 4, 2008 at 4:40 PM, Jukka Zitting [EMAIL PROTECTED] wrote:
Thanks for all the comments, keep 'em coming! Here's an updated
version of the JCR Commons subproject proposal. This version should
address most of the concerns and issues that were raised.
I plan to call a vote on the
On Tue, Dec 9, 2008 at 3:31 PM, Jukka Zitting [EMAIL PROTECTED] wrote:
c) Here's a list of Jira project keys that I think we could use:
* jackrabbit-parent / JCRPARENT
* jackrabbit-jcr-tests / JCRTEST
* jackrabbit-jcr-benchmark / JCRBENCH
* jackrabbit-jcr-rmi / JCRRMI
*
Hi,
On Tue, Dec 9, 2008 at 4:09 PM, Alexander Klimetschek [EMAIL PROTECTED] wrote:
A separate Jira project for each of it? That somehow adds a lot of
projects to Jira, which doesn't feel right to me. I would prefer a
JCRCOMMONS project with each of the maven projects being a subproject.
I
On Tue, Dec 9, 2008 at 4:21 PM, Jukka Zitting [EMAIL PROTECTED] wrote:
Managing separate release cycles within a single Jira project is quite
painful. Just look at the version fields in the SLING project for an
example. And that's just a single release per component so far...
Looks a bit
Hi,
On Tue, Dec 9, 2008 at 5:40 PM, Alexander Klimetschek [EMAIL PROTECTED] wrote:
As it seems, releases are the major driver for this decision, [...]
Yep, the demand for smaller and quicker releases (see [1]) started the
whole component release debate almost a year ago, and with this
proposal
Hi,
Based on earlier discussion [1] I would like to propose that we start
a new Apache JCR Commons subproject within Jackrabbit. See below
what this could mean in practice. As usual, comments are welcome!
COMPONENTS
The JCR Commons subproject would take over the development and
maintenance
On Tue, Dec 2, 2008 at 4:52 PM, Jukka Zitting [EMAIL PROTECTED] wrote:
COMPONENTS
The JCR Commons subproject would take over the development and
maintenance of the following components:
* jackrabbit-jcr-commons
* jackrabbit-jcr-tests
* jackrabbit-jcr-benchmark
*
Hi,
On Tue, Dec 2, 2008 at 5:42 PM, Alexander Klimetschek [EMAIL PROTECTED] wrote:
Do all these projects solely rely on the JCR API?
Some of them have dependencies to other commons projects and/or to
external components. For example jcr-rmi depends on jcr-commons and
slf4j.
They shouldn't be
