On Mon, Mar 31, 2014 at 3:58 PM, Summers Pittman <supittma@redhat.com> wrote:
Y'all,

So there has been some concerns with the complexity of the build
especially where including the Google GCM (push) libraries are
concerned.  Additionally there have been some requests for a separate
"push" module which won't need the full aerogear android library.

The full modularization of the library along with several other
improvements is scheduled for the "2.0" epic.
 
https://issues.jboss.org/browse/AGDROID-236 mentions fix version : 1.4 , should that be updated ?  

So my question is a) Should we make a 2.0 which is only the
modularization sooner and iterate on that a few times before we include
our improvements in a 3.0 or b) Should we create a "fork" project which
is only a push module?  This new project will get merged back into the
main project when we have our complete modularizations.



--
Summers Pittman
>>Phone:404 941 4698
>>Java is my crack.

_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev