This is normal. gradlew is only used from the command line used to start Gradle. When using the daemon it launched Gradle in a JVM but doesn't do anything besides communicating with the Gradle daemon (creating it if necessary) which is in its own VM.
Studio uses the Gradle Tooling API which is a small jar able to communicate with (and create if necessary) the Gradle daemon directly. This is much more efficient than having Studio launch an external process that launches a script which launches a VM that talks to the daemon (in another VM)! What are you trying to do? On Wed, Dec 3, 2014 at 8:18 AM, Pete Winterscheidt <basejump...@gmail.com> wrote: > Hello all, > I am running a customized gradle wrapper, and Android Studio keeps trying > to ignore it. > Since upgrading to the new 1.0 RC 2 every time I do a gradle sync I have > to go to the preferences to reset the configuration to indicate that I am > using a customized wrapper. > > Is there something I can set in a config to prevent this from happening? > Thanks, > Pete > > -- > You received this message because you are subscribed to the Google Groups > "adt-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to adt-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Xavier Ducrohet Android SDK Tech Lead Google Inc. http://developer.android.com | http://tools.android.com Please do not send me questions directly. Thanks! -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to adt-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
