Found it, it's located here: $ANDROID_SDK_PATH/tools/templates/gradle/wrapper
On Wed, Jun 18, 2014 at 8:46 AM, Joe Bowser <bows...@gmail.com> wrote: > Actually, it's not by default, but it does generate a gradle project > if you use the right flags. However, the project structure is > radically different that I'm not sure we want to adopt it. Still, we > can find where the JAR is and copy it out of the Android SDK > directory. > > On Wed, Jun 18, 2014 at 8:45 AM, Joe Bowser <bows...@gmail.com> wrote: >> The Android Dev Tools generate a gradle project by default. Where >> does it store gradle-wrapper? >> >> On Wed, Jun 18, 2014 at 7:59 AM, Josh Soref <jso...@blackberry.com> wrote: >>> Ian Clelland wrote: >>>>But Gradle is a Java project, and so the script invokes Java, and makes >>>>use >>>>of a bundled .jar file, and therein lies the problem: We're not supposed >>>>to >>>>be including compiled JAR files in our repository. >>>> >>>>In this case, the .jar isn't actually part of our code; it's just used by >>>>the build, and including it makes it closer to trivial for developers to >>>>start building Cordova projects. It's easy to recreate, too, once you have >>>>Gradle installed, it's as easy as running "gradle wrapper" to get it to >>>>rebuild the wrapper, jar and all. The catch is that you already have to >>>>have gradle installed for that to work. Egg, meet chicken. >>> >>> Can we cheat and just have a script that uses curl/wget to retrieve Gradle >>> from Apache's dist directory? >>> >>> Or, could we publish Gradle to npm and then have our thing depend on >>> cordova-gradle ? >>>