Right,
we use that mainly because Google does not publish their stuff to maven central. If they would do, we would use that, and perhaps would have also used slightly updated versions.

I was expecting that this dependency needs to go for GCM3 support (e.g. for using topics).  

But, instead of including the GCM-server source into UPS, why not just release it to a custom maven repo (like done in the given URL).
If the GCM-server is fully ASLv2, we could even push it to our JBoss 3rd party repo. 



On Tue, Jul 28, 2015 at 10:01 PM, Summers Pittman <supittma@redhat.com> wrote:
So it looks like UPS is using a jar packaged by "theganyo" https://github.com/theganyo/gcm-server for its Google stuff.  This appears to be a fork of Google's GCM code which was put into maven central.  It is also about two years out of date.

The fork appears to be based on the code here : https://github.com/google/gcm.

For implementing topic support I am probably going to need some functionality from Google's actual code.  Even if I don't I am going to need things feature in neither repository (Constants for error messages in response to topic messaging are immediately apparent).

I am looking for brainstorming around the best way to gracefully move this functionality forward.  I'm thinking drop the ganyo dependency and code and pull the current Google code into UPS.  It is apache licensed.

Thoughts, fears, tomatoes?

Summers

_______________________________________________
aerogear-dev mailing list
aerogear-dev@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