Re: [aerogear-dev] Modularizing the Android Library

On Mar 5, 2014, at 9:33 AM, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: On Wed, Mar 5, 2014 at 3:15 PM, Summers Pittman <supittma(a)redhat.com&gt;wrote: > Earlier in development (pre passos) making the Android SDK into modules > was not a concern (in fact it was an anti-concern). > > Now, however, we have a much more complete project and it is time to > have that discussion. > > Right now we have two BIG questions: > > 1) Do we want to break out interfaces and implementation? > > If we do this then we could reuse a lot of code to make a aerogear-java > as well. > > 2) How granular do we want our modules? > > IE If we break out push into aerogear-android-push would that include > GCM, SimplePush, MQTT, etc in one package or would it look like > android-gcm android-simplepush android-mqtt +1 to those names, and i'm sure you mean aerogear-* :)

> aerogear-android-push-core, aerogear-android-push-mqtt etc. > > Thoughts? > > -- > Summers Pittman > >>Phone:404 941 4698 > >>Java is my crack. > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev