On 01/03/2013, at 10:08 AM, alex.ruiz.05 wrote: > Greetings, > > I'm new to Gradle and I'm learning how the Tooling API work. I wrote a > simple program, similar to one of the samples in the samples/toolingApi. It > has a main method and I'm debugging it to see what it does. > > The issue I found is that I cannot step into the Gradle daemon with the > debugger. I try Google and StackOverflow but nothing really useful. > > I'm using Gradle v 1.5-20130227173909+0000 > > Any help will be greatly appreciated.
There are 2 options: * Running in embedded mode, which you've already discovered. Note that this is currently an internal feature and not completely supported. The embedded daemon is not (or at least, not yet) very well behaved when it comes to sharing a jvm with the owning application - it doesn't handle concurrent builds very well, it messes with the logging levels, system properties, environment variable, and so on. Having said that, it works fine if you're testing stuff out. * Starting the daemon with the appropriate jvm args using LongRunningOperation.setJvmArguments(). This approach is fully supported, but it's not particularly convenient for development work. -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com
