Hi All, we are going to rename the maven group id "org.jboss.gatein" that is not much used in gatein (in testsuite) to "org.gatein.portal" because it is creating issues with eXo's Nexus that forbid to deploy any artifact whose group id prefixed by "org.jboss", which makes the Jenkins build to fail in eXo Software Factory. Of course we will also address the remaining modules, at some point (after 3.4) we will do a mass renaming for renaming the remaining group ids to "org.gatein.portal" as well.

I suppose that it is to reduce the impact to the community and projects built over gatein.

For 3.4 you may have the opportunity to change it everywhere but you have to be in sync with all teams and to communicate it to users and customers in the upgrade note Arnaud On Wed, Jul 18, 2012 at 1:52 PM, Christophe Laprun <claprun(a)redhat.com (mailto:claprun@redhat.com)> wrote: > > On 18 juil. 2012, at 13:43, Arnaud HERITIER wrote: > > > I suppose that it is to reduce the impact to the community and projects built over gatein. > > Makes sense, except that the impact will happen for 3.4 with the partial change and then again in the release that will contain the rest of the changes… Though, I agree that this change is minimal compared to the rest ;) > > Cordialement / Best, > Chris > > == > Principal Software Engineer / JBoss Enterprise Middleware Red Hat, Inc. > Follow GateIn: http://blog.gatein.org / http://twitter.com/gatein > Follow me: http://metacosm.info/metacosm / http://twitter.com/metacosm >