HI, +1 promiting jcr-rmi to prime time.
I'm not sure, whether rebranding to jackrabbit-rmi would be a good choice. It would surely be identified to come from Apache Jackrabbit. In the other it could as well be misinterpreted as being Jackrabbit with RMI access, which it is not. I suggest we leave it as jcr-rmi and identify it properly in the manifest.
-1 rebranding to jackrabbit-rmi. Regards Felix Meschberger Jukka Zitting schrieb:
Hi, As a part of the 0.9 release process I'd like to promote the JCR-RMI component out of the contrib directory. I'd like to make a clear distinction between the components that will be released by the Jackrabbit project and the development "sandbox" that the contrib directory can easily be seen as. I'm focusing on JCR-RMI as a first example because it is already quite mature and widely used and because it is most familiar to me. I'd like to apply the same promoting procedure also to the other mature contrib projects as soon as we reach consensus on how promoting shall be handled. My proposal would be to simply move jcr-rmi one level up from the contrib directory to the main jackrabbit/trunk directory. What do you think? Should jcr-rmi be promoted? Is the above the best way to do it? My initial plan is to include jcr-rmi in the Jackrabbit releases, but it might also make sense to allow independent releace cycles for such components. Which do you think is the better approach? There's also a question related to branding. Should jcr-rmi be renamed to jackrabbit-rmi to better indicate that it is a part of the Jackrabbit project? Such renaming would give a better clue on the origin of the component at the expense of potential misunderstandings of it being a Jackrabbit-specific network layer. BR, Jukka Zitting -- Yukatan - http://yukatan.fi/ - [EMAIL PROTECTED] Software craftmanship, JCR consulting, and Java development
