Peter, On Wed, 2011-08-24 at 22:54 -0700, Peter Niederwieser wrote: > If you have a fairly standard Java/Groovy project, you typically don't have > to do anything to get a working IDEA project. If you use Gradle features > that don't have an equivalent in iDEA (e.g. use custom configurations), you > will have to tweak the IDEA project generation (e.g. map the configuration > to one of the IDEA scopes). I haven't heard of your "problem of the moment" > before. I don't recommend to use the same output directories for IDEA and > Gradle. It's safer to keep them separate (same for Gradle and Eclipse). The > defaults should be fine.
The project is a "bog standard" Maven/Gradle structured project with only Java and TestNG (which may be the problem?). The Bazaar branch of this can be branched from http://www.russel.org.uk/Bazaar/ADS (no browsing, sorry) or I also have it on Launchpad at https://code.launchpad.net/~russel/devjavasoft/trunk which is browseable. I'm afraid my "problem of the moment" seems to be totally reproducible. Contrary to your expectation, the default IntelliJIDEA project for a TestNG based Java project doesn't work. :-(( I agree about not sharing output directories, hence my reply to Hani. -- Russel. ============================================================================= Dr Russel Winder t: +44 20 7585 2200 voip: sip:[email protected] 41 Buckmaster Road m: +44 7770 465 077 xmpp: [email protected] London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
signature.asc
Description: This is a digitally signed message part
