<div dir="ltr">Or, we skip the plugin, and continue to rely on the sender_id / project_number, like now ?<div><br></div><div>I think I am a bit sceptical if this plugin makes us go a route we perhaps don't want ? </div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Apr 26, 2016 at 3:14 AM, Matthias Wessendorf <span dir="ltr"><<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">How is the regerence impl. (gcm-playground) solving this?<div class="HOEnZb"><div class="h5"><br><br>On Monday, 25 April 2016, Summers Pittman <<a href="mailto:supittma@redhat.com" target="_blank">supittma@redhat.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">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.<div><br></div><div>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.</div><div><br></div><div>Thoughts?</div><div><br></div><div>Summers</div></div>
</blockquote><br><br></div></div><span class="HOEnZb"><font color="#888888">-- <br>Sent from Gmail Mobile<br>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">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>