On Thu, 2008-10-23 at 14:01 +0200, Hans Dockter wrote: > Wouldn't it work to use: ./gradlew -Dskip.test -Dskip.integTest - > Dskip.userguide -Dskip.javadoc -Dskip.groovydoc -Dskip.archive_all- > jdk14_zip -Dskip.archive_src_zip clean install to install a new > gradle version. Then you can start the same build with gradle to see > the effects of the new version.
I guess I was hoping for something less cumbersome than having to do a full install and then test, but it will work. > The way I solve this usually is to use my IDE to do the build. For > how to do this with IntelliJ see: http://docs.codehaus.org/display/ > GRADLE/How+to+run+the+Gradle+project+in+IntelliJ+against+any+Gradle > +build It is unfortunate that this still has to be done manually and > we don't have an intellij task that does this. I still think Emacs+Bash is a better IDE that any of IntelliJ IDEA, Eclipse or NetBeans -- but that is my problem :-) -- Russel. ==================================================== Dr Russel Winder Partner Concertant LLP t: +44 20 7585 2200, +44 20 7193 9203 41 Buckmaster Road, f: +44 8700 516 084 London SW11 1EN, UK. m: +44 7770 465 077
signature.asc
Description: This is a digitally signed message part
