Re: [aerogear-dev] Modularizing the Android Library
I believe there should be a POM depchain for users that are willing just to use
aerogear-android and modular dependencies are for more experienced users.
Similarly to *Adding ShrinkWrap Resolvers to your project* at
https://github.com/shrinkwrap/resolver/blob/master/README.asciidoc
I'm not sure how nicely that would play with Gradle though.
Karel
On Wed, 05 Mar 2014 09:15:27 -0500
Summers Pittman <supittma(a)redhat.com> 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
aerogear-android-push-core, aerogear-android-push-mqtt etc.
Thoughts?