On Tue, Jan 13, 2009 at 3:10 PM, Felix Meschberger <[email protected]> wrote: >> Not sure if we'd rather keep the Jackrabbit reference here, since the >> JCR commons is still part of the Jackrabbit project. That would also >> be backwards-compatible. The main indicator would then be the 4th part > > While I agree with your fears with respect to backwards compatibility, > your solution does not help ;-) > > The jackrabbit-jcr-commons project lives in the o.a.jackrabbit > namespace. So regardless of where we "inject" the "jcr" part, we will > break backwards compatibility, but ...
You are right, once we change something, we break backwards compatibility. But I was thinking maybe we don't have to in this case... but as nothing has a "o.a.jackrabbit.jcr" this is thinking is obsolete ;-) > I have a slight preference for this proposal, too. After all, this is > Apache Jackrabbit speaking ;-) Yup, some branding is good! Regards, Alex -- Alexander Klimetschek [email protected]
