[aerogear-dev] Modularization and Push

Hylke Bons hbons at redhat.com
Mon Mar 31 11:53:43 EDT 2014


Not that I can help, but just wanted to say this is good news!
Other than being more modular it makes the project as a while easier to 
understand and present. :)

Hylke


On 31/03/2014 14:58, Summers Pittman 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.
>
> 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.
>
>
>



More information about the aerogear-dev mailing list