Hi, Jukka Zitting schrieb: > Hi, > > I started setting up the new JCR Commons subproject by using the > JCR-RMI component as the first example. Here are the steps I've taken > so far: > > 1) Create the JCRRMI project in Jira. > 2) Migrate all open "jackrabbit-jcr-rmi" issues from JCR to JCRRMI. > 3) Create the repos/asf/jackrabbit/commons/jcr-rmi directory in svn. > 4) Copy trunk/jackrabbit-jcr-rmi to commons/jcr-rmi/trunk > 5) Modify the JCR-RMI POM to work outside the main Jackrabbit build. > > Here's what I still plan to do over the next few weeks/months: > > 6) Rename the org.apache.jackrabbit.rmi package to org.apache.jcr.rmi. > 7) Prepare and release JCR-RMI 2.0. > 8) Replace old jackrabbit-jcr-rmi with an external dependency to the > new 2.0 release of JCR-RMI. > 9) Remove the jackrabbit-jcr-rmi component from the JCR project in Jira. > > Feel free to comment or question any of these steps, I may well be > overlooking something or otherwise going in the wrong direction.
Looks good so far. But I would also modify the jackrabbit projects to refer to the latest released jcr-rmi artifact instead of to the 1.6-SNAPSHOT one. This way we start with a well-known behaviour for the Jackrabbit itself right away. Likewise I strongly suggest to revert to using the latest releases jackrabbit-jcr-commons in the Jackrabbit project until jcr-commons 2.0 is released. And so forth for the rest of the new commons projects. Regards Felix > > If this migration works well for JCR-RMI, we can replicate it with the > other JCR Commons components. > > BR, > > Jukka Zitting >
