On Oct 23, 2008, at 1:19 PM, Russel Winder wrote:
OK, we have a "chicken and egg" problem here. Debugging the Gradle
build appears to be impossible because a previous version of Gradle is
used to do the build. So I am unable to put probes (or even sleeps)
into the Gradle source to find out what is going on because this
version
is not then used for the build.
I guess this must be a standard problem and I have just failed to know
what the right trick is.
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.
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.
- Hans
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
