<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Jun 30, 2013 at 11:54 PM, Summers Pittman <span dir="ltr"><<a href="mailto:supittma@redhat.com" target="_blank">supittma@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Y'all,<br>
<br>
pilhuhn asked on Twitter if we were planning to support the new aar<br>
package format in AeroGear's Android library. Matzew suggested to take<br>
it to the mailing list so I will run with it for now.<br></blockquote><div><br></div><div><br></div><div style>thanks!</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
First an introduction. Aar is Google's new binary package format for<br>
Android libraries. It is what their Gradle plugin looks for when it<br>
fetches libraries. For those of you who havn't experienced the joy of<br>
using Android Library Projects with Android Application projects this<br>
fixes a whole host of maintainability and usability problems. Matzew<br>
can probably explain the n00b experience better, but you should be<br>
fluent in angry, angry German.<br></blockquote><div><br></div><div>:-) </div><div style><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
Now for the challenges. We use Maven to build AGDroid and the<br>
maven-android-plugin does not yet support aar. </blockquote><div><br></div><div><br></div><div>Not sure, but would it help if, for the Android bits, we move to Gradle (and away from Maven) ? <br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Also in some Googling<br>
last week I could find 0 documentation for the file format. Right now<br>
the only way to make an aar build is to export an Eclipse Android<br>
project and import it into Android Studio and let it build the aar for<br>
you. This can then be packaged into maven central but is really labor<br>
intensive.<br>
<br>
Also the only thing which supports using aar is Android Studio /<br>
Google's Gradle build stuff. Other than being on the cutting cutting<br>
edge (and having a nice project feather in our cap) I don't really see<br>
what this gets us right now.<br>
<br>
With that said I would like to put energy toward this.<br>
<br>
For now I propose we start building an aar as part of the release process.<br>
Eventually I would like to lend a hand to the android-maven-plugin<br>
project so they can export aars.<br>
Right now I do NOT think we should look at porting the AGDroid source<br>
project from maven to Android Studio.<br>
<br>
Thoughts?<br>
<br>
Summers<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>