<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Totally agree, we have to get rid of the gradle workaround, it should not be necessary to edit the generated platform directories. I see a third option though on the 4.0 release of the android platform aar support will be added and one could add a framwork dependency with type aar. We could also opt to wait for this release. But I’m +1 on making the oath2 plugin like the google play services plugin so that it works with `older` versions as well.<div class=""> <br class=""><div class=""><blockquote type="cite" class=""><div class="">On 5 Mar,2015, at 23:00 , Brian Leathem <<a href="mailto:bleathem@gmail.com" class="">bleathem@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="content-type" content="text/html; charset=utf-8" class="">
<div text="#000000" bgcolor="#FFFFFF" class="">
Hello gear-heads,<br class="">
<br class="">
The aerogear-cordova-oauth2 project currently has a requirement to
be built with gradle, in order to be able to build the aerogear
oauth2 dependencies. This affects users, as once they add the
aeorgear cordova plugin to their project, they have to switch to a
gradle-based build.<br class="">
<br class="">
I propose we look at what was done with google-play-services as a
means of working around this gradle requirement. There are two ways
to introduce a dependency to google-play-services in your cordova
project/plugin:<br class="">
<br class="">
a) Add a maven dependency:
<meta http-equiv="content-type" content="text/html; charset=utf-8" class="">
com.google.android.gms:play-services:4.0.30@aar<br class="">
b) Add a cordova plulgin dependency: com.google.playservices<br class="">
<br class="">
a) can be achieved only after following the
how-to-build-aerogear-android [1] instructions, so an even bigger
inconvenience for users.<br class="">
<br class="">
b) on the other hand is as simple as:<br class="">
<br class="">
i) running "cordova plugin add com.google.playservices" in your
project folder<br class="">
or<br class="">
ii) adding "com.google.playservices" as a dependency to the android
section of your plugin's plugin.xml file [2].<br class="">
<br class="">
This is made possible because the google-play-services binaries are
published as a cordova plugin via a project hosted on github [3].<br class="">
<br class="">
I propose we create a project similar to [3], to hold the aerogear
android dependencies. Call it "aerogear-android-services" for the
sake of this argument. We would then register this project with
cordova so the aerogear-cordova-oauth2 plugin can have a dependency
on the aerogear-android-services cordova plugin, rather then the
maven/gradle dependency we have now. This would then alleviate the
aerogear-cordova-oauth2 from needing to be built with gradle.<br class="">
<br class="">
Thoughts?<br class="">
<br class="">
[1]
<a class="moz-txt-link-freetext" href="https://aerogear.org/docs/guides/aerogear-android/how-to-build-aerogear-android/">https://aerogear.org/docs/guides/aerogear-android/how-to-build-aerogear-android/</a><br class="">
[2]
<a class="moz-txt-link-freetext" href="https://github.com/bleathem/cordova-oauth-google-services/blob/master/plugin.xml#L28">https://github.com/bleathem/cordova-oauth-google-services/blob/master/plugin.xml#L28</a><br class="">
[3] <a class="moz-txt-link-freetext" href="https://github.com/MobileChromeApps/google-play-services">https://github.com/MobileChromeApps/google-play-services</a><br class="">
<br class="">
</div>
_______________________________________________<br class="">aerogear-dev mailing list<br class=""><a href="mailto:aerogear-dev@lists.jboss.org" class="">aerogear-dev@lists.jboss.org</a><br class=""><a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" class="">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></div></blockquote></div><br class=""></div></body></html>