I think this is a problem with the Eclipse integration, rather than a general IDE problem. Using IntelliJ IDEA, I have no problems sharing the output directories and cannot imagine why I would want to keep them separate. Why build the files twice?
If I've built the entire project using gradle, why build it again if I want to run some tests from within the IDE? The problem seems to be Eclipse and its policy to build using its own compiler. If I understand correctly, it is not possible to change this to javac (or any other custom compiler), which would probably eliminate the problem. I would much rather prefer to keep the current solution, which requires a workaround for the faulty Eclipse integration, rather than defaulting to a sub-optimal structure. Regards, Steinar On Tue, Jan 11, 2011 at 9:56 AM, Jeppe Nejsum Madsen <[email protected]>wrote: > Adam Murdoch <[email protected]> writes: > > > Hi, > > > > The 'eclipse' and 'idea' plugins configure the IDE to compile classes > into the same directories as Gradle, ie build/classes/main and > build/classes/test. > > > > I think this is not such a great idea. Instead, I think these plugins > should configure the IDE to compile classes into different locations. > Probably whatever the default happens to be for the target IDE. > > > > Agreed. I always change the output dir in Eclipse for the same > reason. Not sure if this is out of habit though :-) But Eclipse is not > always happy when files are changed from outside eclipse. > > /Jeppe > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > -- Steinar Haugen Gausengate 12 3080 Holmestrand Phone: +47 932 08 373 Email (p): [email protected] Email (w): [email protected] Web: http://www.haugenconsulting.no
