<div dir="ltr">Hi Folks,<div><br></div><div>Just to y'all know, that is what we are planning for android modules</div><div><br></div><div><div>aerogear-android-core (pipe, auth, autz)</div><div>aerogear-android-store</div>
<div>aerogear-android-push</div><div>aerogear-android-security|encrypt (keyservices)</div><div>aerogear-android-offline</div><div>aerogear-android-sync</div><div>aerogear-android-messaging</div></div><div><br></div><div>
wdyt?</div>
<div><br></div><div>-- Passos</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Mar 6, 2014 at 10:38 AM, Karel Piwko <span dir="ltr"><<a href="mailto:kpiwko@redhat.com" target="_blank">kpiwko@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I believe there should be a POM depchain for users that are willing just to use<br>
aerogear-android and modular dependencies are for more experienced users.<br>
<br>
Similarly to *Adding ShrinkWrap Resolvers to your project* at<br>
<a href="https://github.com/shrinkwrap/resolver/blob/master/README.asciidoc" target="_blank">https://github.com/shrinkwrap/resolver/blob/master/README.asciidoc</a><br>
<br>
I'm not sure how nicely that would play with Gradle though.<br>
<span class="HOEnZb"><font color="#888888"><br>
Karel<br>
</font></span><div class="im HOEnZb"><br>
On Wed, 05 Mar 2014 09:15:27 -0500<br>
Summers Pittman <<a href="mailto:supittma@redhat.com">supittma@redhat.com</a>> wrote:<br>
<br>
> Earlier in development (pre passos) making the Android SDK into modules<br>
> was not a concern (in fact it was an anti-concern).<br>
><br>
> Now, however, we have a much more complete project and it is time to<br>
> have that discussion.<br>
><br>
> Right now we have two BIG questions:<br>
><br>
> 1) Do we want to break out interfaces and implementation?<br>
><br>
> If we do this then we could reuse a lot of code to make a aerogear-java<br>
> as well.<br>
><br>
> 2) How granular do we want our modules?<br>
><br>
> IE If we break out push into aerogear-android-push would that include<br>
> GCM, SimplePush, MQTT, etc in one package or would it look like<br>
> aerogear-android-push-core, aerogear-android-push-mqtt etc.<br>
><br>
> Thoughts?<br>
><br>
<br>
</div><div class="HOEnZb"><div class="h5">_______________________________________________<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>
</div></div></blockquote></div><br></div></div>