<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Aug 20, 2013 at 10:14 PM, Bruno Oliveira <span dir="ltr"><<a href="mailto:bruno@abstractj.org" target="_blank">bruno@abstractj.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">We already have the side effects, his name is<br>
maven-android-sdk-deployer.</blockquote><div><br></div><div>:-) I'd even say 'nasty' side effects :-)</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
So if Gradle will help to get rid off it,<br>
still +1<br></blockquote><div><br></div><div>yep - same feelings.</div><div><br></div><div>+1 here</div><div> </div><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>
Summers Pittman wrote:<br>
> On 08/20/2013 08:35 AM, Karel Piwko wrote:<br>
>> Do you know how Gradle stands for IDE support? Does it simplify Android<br>
>> Development for Eclipse/JBDS/IntelliJ?<br>
> Gradle support is excellent in IntelliJ. Acceptable in NetBeans (by<br>
> NetBeans' standards), and I don't know about Eclipse because Eclipse is<br>
> a pain in the ass with third part build tools. It looks like Spring STS<br>
> is providing a Gradle for Eclipse plugin but I havn't used it.<br>
><br>
> Until everyone is using Gradle and Android Studio we still will have to<br>
> maintain maven (for apklib) but the golden scenario for starting<br>
> out/green field development will be Gradle.<br>
><br>
> Now I may get into the woods on this and find out it has a horrible side<br>
> effect, but right now it should simplify the life of a developer.<br>
><br>
> Summers<br>
><br>
> PS One important note is that this would be hitching us harder to<br>
> Google's tooling cart and they have been known to dump products in the<br>
> ocean with only a few months of notice.<br>
>> Karel<br>
>><br>
>> On Mon, 19 Aug 2013 10:48:25 -0400<br>
>> Summers Pittman <<a href="mailto:secondsun@gmail.com">secondsun@gmail.com</a>> wrote:<br>
>><br>
>>> Y'all,<br>
>>><br>
>>> In the last release we had some trouble at the end. People were having<br>
>>> trouble building aerogear-android because the android-sdk-deployer<br>
>>> project had a couple of "small" problems. Mainly there was an issue with<br>
>>> one of the deployers submodules (and it had to be disabled by hand) and<br>
>>> the deployer itself isn't compatible with maven 3.1.0. I don't want to<br>
>>> include in the build instructions for aerogear "download this old<br>
>>> version of Maven and then edit the pom of this third party project".<br>
>>><br>
>>> The easiest way to remove our dependency on the deployer is to start<br>
>>> using Google's gradle build system. The Android SDK has packages for<br>
>>> deploying the necessary repositories so that our build can consume them<br>
>>> and we can use the gradle wrapper to keep our users from having to<br>
>>> install yet more software.<br>
>>><br>
>>> So where does this leave maven? Unfortuantely it is still necessary to<br>
>>> build the apklib file (as far as I know), but it won't be necessary to<br>
>>> actually USE the project anymore.<br>
>>><br>
>>> wdyt?<br>
>>><br>
>>> Summers<br>
>>><br>
>>><br>
>>> _______________________________________________<br>
>>> aerogear-dev mailing list<br>
>>> <a href="mailto: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>
>> _______________________________________________<br>
>> aerogear-dev mailing list<br>
>> <a href="mailto: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>
><br>
> _______________________________________________<br>
> aerogear-dev mailing list<br>
> <a href="mailto: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>
<br>
</div></div><span class="HOEnZb"><font color="#888888">--<br>
abstractj<br>
<br>
<br>
</font></span><br>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto: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 clear="all"><div><br></div>-- <br>Matthias Wessendorf <br>
<br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
</div></div>