Hello Thomas, Without replying in line below, I am wondering whether you did see Jukka's mail from some time ago [1] (actually send twice):
'[jr3] Rethinking our Jackrabbit 3.0 roadmap' I am not in a position to judge it well enough (I will chime in when discussion touches my knowledge areas), but before going into the questions you ask yourself below, I think first, the way jr3 will be developed should be addressed. So, I think, this discussion should first be about the proposal Jukka made in his mail. Regards Ard [1] http://mail-archives.apache.org/mod_mbox/jackrabbit-dev/201011.mbox/%3c9c0fc4c8e9c29945b01766fc7f9d389816bfcb0...@eurmbx01.eur.adobe.com%3e On Wed, Dec 1, 2010 at 10:07 AM, Thomas Mueller <muel...@adobe.com> wrote: > Hi, > > At some point we need to discuss where to start with Jackrabbit 3. I guess > the most important deliverable is an embedded (not server; that is, no > remoting) JCR 2.0 repository that uses a database as the storage backend. > This would be 'one project' as I wrote in the subject (and one jar file). > > > The question is how we want to re-use existing Jackrabbit 2 modules (or > generally "code") within Jackrabbit 3. Personally, at the beginning I > would favor "copy code when needed", because only this approach allows to > really refactor the code without risking to break Jackrabbit 2. I think we > should continue to develop and change Jackrabbit 2 as if Jackrabbit 3 > doesn't exist, at least at the beginning (things may be different later > on). > > Regards, > Thomas > > -- Hippo Europe • Amsterdam Oosteinde 11 • 1017 WT Amsterdam • +31 (0)20 522 4466 Hippo USA Inc • 755 Baywood Drive • Second Floor • Petaluma, CA • 94954 USA • Phone +1 (707) 658-4535 Canada • Montréal 5369 Boulevard St-Laurent • Montréal QC H2T 1S5 • +1 (514) 316 8966 www.onehippo.com • www.onehippo.org • i...@onehippo.com
