On 11/01/2011, at 10:18 AM, John Murph wrote: > Why do you think this is not such a great idea?
It's mainly a issue of robustness, I think. Neither IDE is 100% reliable in the face of other tools scribbling over their compiler output. Gradle is very robust in this respect, because it takes a snapshot of the classes directory (ie which files are present, and what is the hash of their content) and can detect and clean up external changes and recreate the output files accurately. Having said that, I'm almost certain there are accuracy issues lurking there. > This way, if I build in Gradle, I can run/debug from the IDE. Similarly, I > can build in the IDE and run from Gradle. I don't really understand what you mean here. You can still do these things when the output directories are separated. Or do you mean that you can build in Gradle and then run against the Gradle generated class files in the IDE? -- Adam Murdoch Gradle Developer http://www.gradle.org CTO, Gradle Inc. - Gradle Training, Support, Consulting http://www.gradle.biz
