<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Mar 31, 2014 at 5:07 PM, Karel Piwko <span dir="ltr"><<a href="mailto:kpiwko@redhat.com" target="_blank">kpiwko@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I'd prefer a) unless you plan to regularly release milestones of b) into Maven<br>
Central. Relying on snapshots in demos and tests is a PITA.</blockquote><div><br></div><div>of course there will be an "android-push.jar" (library) on maven central</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
And this looks like<br>
a lot of effort, so branch might be living its own life for a very long time.<br>
<span class="HOEnZb"><font color="#888888"><br>
Karel<br>
</font></span><div class="im HOEnZb"><br>
On Mon, 31 Mar 2014 09:58:57 -0400<br>
Summers Pittman <<a href="mailto:supittma@redhat.com">supittma@redhat.com</a>> wrote:<br>
<br>
> Y'all,<br>
><br>
> So there has been some concerns with the complexity of the build<br>
> especially where including the Google GCM (push) libraries are<br>
> concerned. Additionally there have been some requests for a separate<br>
> "push" module which won't need the full aerogear android library.<br>
><br>
> The full modularization of the library along with several other<br>
> improvements is scheduled for the "2.0" epic.<br>
><br>
> So my question is a) Should we make a 2.0 which is only the<br>
> modularization sooner and iterate on that a few times before we include<br>
> our improvements in a 3.0 or b) Should we create a "fork" project which<br>
> is only a push module? This new project will get merged back into the<br>
> main project when we have our complete modularizations.<br>
><br>
><br>
><br>
<br>
</div><div class="HOEnZb"><div class="h5">_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>
sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
</div></div>