Hi, Hmm, on second thought -- maybe moving to trunk is fine, but in a separate clearly separate area and not included in any upcoming release.
This is work in progress and interested parties -- hopefully also people providing code -- are developers not end users. Regards Felix On 14.05.2010 18:43, Felix Meschberger wrote: > Hi > > As much as I understand that we should push JR 3 forward, I agree with > Angela's position. > > I don't think that adding JR3 as a techno preview in upcoming JR 2 will > do any good -- except making the release process and understanding the > code even more complex. > > Regards > Felix > > On 14.05.2010 08:25, Angela Schreiber wrote: >> hi jukka >> >>> Thomas has done some nice work with the jackrabbit-j3 prototype in the >>> sandbox. To make this codebase easily available to other developers >>> and to allow better reuse of existing Jackrabbit code and integration >>> with things like jackrabbit-standalone, I propose that we move the >>> component from the sandbox to Jackrabbit trunk. This means that the >>> component would be included as a technology preview in future 2.x >>> releases and that we'd include it in our normal continuous integration >>> builds. The downside is the increased build time in trunk. >> >> not sure... i have the impression that it is too early to move >> the prototype out of the sandbox. >> >> and i don't fully understand your arguments for the move: reuse >> of existing code is achieved by adding dependencies to other >> modules in either way, isn't it? and furthermore, i don't understand >> why a sandbox project wasn't easily available... my criteria for a >> move into trunk would rather be: this prototype isn't a prototype any >> more and we feel comfortable to include it into your regular release >> cycle. >> >> regards >> angela >> >>> WDYT? >>> >>> BR, >>> >>> Jukka Zitting >>> >> >>
