Hi Julien,
We (The JCR Team) can change of Groovy version at the JCR level, but is-it safe to rely on 1.7 which is stil AFAIK a beta version? Or maybe you would like to rely on the last stable version of Groovy which is 1.6.5? Please, answer as soon as possible as it will be part of the next sprint that begins tomorrow.
On Sun, Oct 25, 2009 at 12:44 AM, Arnaud HERITIER <aheritier@gmail.com> wrote:I think it is to put the new version of groovy in the depMgt of the portal pom, for the build part.For the assembly part you have to update the module.js :Actually it is the 1.5.7
Cheers,
Arnaud
# Arnaud Héritier
# Software Factory Manager
# eXo Platform
# http://www.exoplatform.com
# http://blog.aheritier.net
On Sun, Oct 25, 2009 at 1:36 AM, Julien Viet <julien@julienviet.com> wrote:Hi Dimitri,
I want to upgrade the Groovy dependency in the performance branch. As
this library is pulled from the JCR dependencies, I was wondering what
is the correct thing to do update the packaging of Groovy.
cheers
Julien
_______________________________________________
gatein-dev mailing list
gatein-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/gatein-dev
_______________________________________________
gatein-dev mailing list
gatein-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/gatein-dev
--
Nicolas Filotto
JCR Product Manager
Project Manager
eXo Platform SAS
nicolas.filotto@exoplatform.com
+33 (0)6 31 32 92 19