For Android maven is irrelevant since google's stuff is based on ant directly and moving to gradle nowadays. For the backend, <span></span>JBoss tools are maven based at least for examples etc maven should be the choice. OTOH I am not sure if there is a real need to move to Gradle for server side at all, I do not think we are building android and the backend together<div>
--</div><div>Gorkem<br><br>On Thursday, June 6, 2013, Douglas Campos wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Tue, May 28, 2013 at 01:17:46PM -0400, Summers Pittman wrote:<br>
> On the high end of work we port the build system to the Gradle build<br>
> system used in Android Studio. This will eventually be done, but we<br>
> probably shouldn't make it a priority until after AS and Android's<br>
> Gradle build system have become finalized.<br>
GAAAAAH<br>
<br>
Thought gradle had a maven compatibility mode that we could make use of<br>
:P<br>
<br>
--<br>
qmx<br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="javascript:;" onclick="_e(event, 'cvml', 'aerogear-dev@lists.jboss.org')">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
</blockquote></div><br><br>-- <br><div dir="ltr">--<br>Gorkem<br></div><br>