Re: [rmi] JCR-RMI 2.0.0 release plan

2009-04-07 Thread Jukka Zitting
Hi, I had a quick chat with Angela about the versioning strategy, and she made a good point that calling the next release 2.0 will be confusing as we're not yet upgrading to JCR 2.0 or doing any other major changes to the codebase. Only the project structure is changing. So, would it make more

Re: [rmi] JCR-RMI 2.0.0 release plan

2009-04-07 Thread Felix Meschberger
Hi, Jukka Zitting schrieb: Hi, I had a quick chat with Angela about the versioning strategy, and she made a good point that calling the next release 2.0 will be confusing as we're not yet upgrading to JCR 2.0 or doing any other major changes to the codebase. Only the project structure is

Re: [rmi] JCR-RMI 2.0.0 release plan

2009-04-06 Thread Felix Meschberger
Hi, Good thing. I just checked it out and have a quick look at it. Here is a first impression: I think, we probably don't need to export everything from this bundle (yet, testing this would be important). Rather we should probably export the most important factory classes: The Server and the

Re: [rmi] JCR-RMI 2.0.0 release plan

2009-04-06 Thread Jukka Zitting
Hi, On Mon, Apr 6, 2009 at 7:50 PM, Felix Meschberger fmesc...@gmail.com wrote: I think, we probably don't need to export everything from this bundle (yet, testing this would be important). Rather we should probably export the most important factory classes: The Server and the Client factories

[rmi] JCR-RMI 2.0.0 release plan

2009-04-01 Thread Jukka Zitting
Hi, I'd like to start releasing individual JCR Commons components so we can simplify the Jackrabbit core before the 1.6 release. JCR-RMI is the component I've been using for setting up things in JCR Commons. I think the component is getting close to being released by itself, so I'd like anyone