<div style="font-family: Helvetica; font-size: 13px; ">there will be already a migration of eXo stack to AMD dependencies, so it would be best to not do 2 migrations at the same time. At least for 3.4cr1 we will not do it, if the migration is fully done then it would be an option to do it for 3.4 in September.<br></div>
<div><div><br></div><div>Julien Viet</div><div>julienviet.com</div><div><br></div></div>
<p style="color: #A0A0A8;">On Wednesday, July 18, 2012 at 2:00 PM, Arnaud HERITIER wrote:</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div>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<div><br></div><div>Arnaud<br><br><div>
On Wed, Jul 18, 2012 at 1:52 PM, Christophe Laprun <span dir="ltr"><<a href="mailto:claprun@redhat.com" target="_blank">claprun@redhat.com</a>></span> wrote:<br><blockquote type="cite"><div>
<div><br>
On 18 juil. 2012, at 13:43, Arnaud HERITIER wrote:<br>
<br>
> I suppose that it is to reduce the impact to the community and projects built over gatein.<br>
<br>
</div>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 ;)<br>
<div><div><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>
</div></div></div></blockquote></div><br></div>
</div></div></span>
</blockquote>
<div>
<br>
</div>