Re: [aerogear-dev] Google Service Gradle Plugin
Or, we skip the plugin, and continue to rely on the sender_id /
project_number, like now ?
I think I am a bit sceptical if this plugin makes us go a route we perhaps
don't want ?
On Tue, Apr 26, 2016 at 3:14 AM, Matthias Wessendorf <matzew(a)apache.org>
wrote:
How is the regerence impl. (gcm-playground) solving this?
On Monday, 25 April 2016, Summers Pittman <supittma(a)redhat.com> wrote:
> I am currently working on setting up support for consuming the
> google-services.json file for our AeroGear Android Push. I can parse the
> file to extract the push values from it at runtime if the file is in the
> assets folder; however, the Google services plugin expects this to be in
> the project flavor root and thus outside of the classpath.
>
> What do you guys think? Ideally we wouldn't be dependent on Google's
> plugin and would put this file in assets. However if you use Google's
> services above and beyond push then we will either a) need to duplicate the
> file or b) intelligently detect if the plugin was used to build the project
> and consume the file as appropriate.
>
> Thoughts?
>
> Summers
>
--
Sent from Gmail Mobile
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
Attachments:
- attachment.html (text/html — 2.2 KB)