[aerogear-dev] Modularization and Push

[Matthias Wessendorf]

On Mon, Mar 31, 2014 at 3:58 PM, Summers Pittman <supittma at 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.
>
> 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.
>

I am fine in having a branch, where the push related modularizations live
in.

Once we are ready for an overall modularization (aka 2.0 timeframe), let's
do it than.

but yeah - for now the fork/branch sounds good for me

-M



>
>
>
> --
> Summers Pittman
> >>Phone:404 941 4698
> >>Java is my crack.
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140331/92af039f/attachment.html