brix + modeshape 3.1.1

48 views
Skip to first unread message

ati.rosselet

unread,
Mar 28, 2013, 5:03:14 PM3/28/13
to brix-cms...@googlegroups.com
Hi, does anyone have a brix version that runs on Modeshape3 instead of jackrabbit?  Is this still in the works.. or planned? Any idea of when/if it will be workable?
Thanks
Ati

Korbinian

unread,
Apr 18, 2013, 5:27:14 AM4/18/13
to brix-cms...@googlegroups.com
actually yes, I got one on my dev machine - modeshape 3 runs nice with brix, trouble is more that modeshape 3 isnt yet stable enough IMHO, suggest to wait till 3.2 that'll be out soon; Ill push up a modeshape 3.2 compatible version then as I plan to upgrade it myself - we currently still run the 2.8 branch with brix

Regards

Ati Rosselet

unread,
Apr 18, 2013, 9:23:39 AM4/18/13
to brix-cms...@googlegroups.com
cheers, that would be great.  I thought I had all bases covered, but brix just kept on complaining that it couldn't find a brix repository (bx_....)... even though it was there... I probably missed something trivial in the Utils...
Thanks
Ati


--
You received this message because you are subscribed to the Google Groups "brix-cms-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to brix-cms-discu...@googlegroups.com.
To post to this group, send email to brix-cms...@googlegroups.com.
Visit this group at http://groups.google.com/group/brix-cms-discuss?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Korbinian

unread,
Jul 24, 2013, 4:34:49 PM7/24/13
to brix-cms...@googlegroups.com
Just a note: I'm still on it and the soon the be released ModeShape 3.4 should be the first ModeShape 3.x version that is fully compatible with brix cms. However, Brix CMS needs a fixed set of CND definitons as the original ones are in violation of the JCR 1/ JCR 2 api, however, this would not harm any own code, its mere a configuration fix;

Korbinian

unread,
Jul 24, 2013, 4:35:59 PM7/24/13
to brix-cms...@googlegroups.com
To fast to send: they are not in API violation, but in violation of the JCR 1.0 and 2.0 specification!
Reply all
Reply to author
Forward
0 new messages