I suppose that it is to reduce the impact to the community and projects built over gatein.<div><br></div><div>Arnaud<br><br><div class="gmail_quote">On Wed, Jul 18, 2012 at 12:38 PM, Christophe Laprun <span dir="ltr"><<a href="mailto:claprun@redhat.com" target="_blank">claprun@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5"><br>
On 18 juil. 2012, at 09:17, Julien Viet wrote:<br>
<br>
> Hi All,<br>
><br>
> 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.<br>
><br>
> 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.<br>
<br>
</div></div>Why not do everything at the same time, which would make more sense?<br>
<br>
Cordialement / Best,<br>
Chris<br>
<br>
==<br>
Principal Software Engineer / JBoss Enterprise Middleware Red Hat, Inc.<br>
Follow GateIn: <a href="http://blog.gatein.org" target="_blank">http://blog.gatein.org</a> / <a href="http://twitter.com/gatein" target="_blank">http://twitter.com/gatein</a><br>
Follow me: <a href="http://metacosm.info/metacosm" target="_blank">http://metacosm.info/metacosm</a> / <a href="http://twitter.com/metacosm" target="_blank">http://twitter.com/metacosm</a><br>
<br>
</blockquote></div><br></div>