Hi, Alexander Klimetschek schrieb: > On Mon, Jan 12, 2009 at 11:57 PM, Jukka Zitting <[email protected]> > wrote: >> I'd like to start using org.apache.jcr as the package root and Maven >> groupId of the components in the new JCR Commons subproject to clarify >> the distinction between "Jackrabbit, the content repository" and the >> generic JCR tools we'll have in JCR Commons. > > 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 ... Since jackrabbit-jcr-commons (or jcr-commons, right ?) depends on nothing from Jackrabbit this does not hurt, since bot libraries will ultimately be able to live side by side because there package-space does not overlap. > in the package name, not sure if this one is consisten across the > components that go into jcr commons (that could IMHO be > "o.a.jackrabbit.jcr"). I have a slight preference for this proposal, too. After all, this is Apache Jackrabbit speaking ;-) Regards Felix
