Hi, everyone! Unfortunately, my introduction to this list has to be due to
an issue we are having.
We started using Gradle with 0.9-rc-1. We have a number of regression tests
that are executed as subprocesses from a main gradle script, and everything
was working great -- it was a vast improvement over either the Ant or Maven
builds we've previously run. However, we recently upgraded to 0.9.1 (and
have also tried 0.9.2 and the latest code from the git repository for that
matter), and we no longer get the System.out from the subprocess.
As a test, I created the simplest build.gradle I could think of to show the
error:
task testOutput << {
String javaHome = System.env['JAVA_HOME']
Process p = ["${javaHome}/bin/java",'-version'].execute()
p.consumeProcessOutput(System.out, System.err)
p.waitFor()
}
On my Linux system (Fedora 13), I get the following:
bcarlson@bcarlsondt:~/tmp$ gradle testOutput
:testOutput
java version "1.6.0_17"
Java(TM) SE Runtime Environment (build 1.6.0_17-b04)
Java HotSpot(TM) 64-Bit Server VM (build 14.3-b01, mixed mode)
BUILD SUCCESSFUL
Total time: 7.396 secs
This works great, just as I would expect. However, on our main build
machine, which is Windows Server 2008 SP2, I get the following (with the
exact same build.gradle)
D:\temp>gradle testOutput
:testOutput
BUILD SUCCESSFUL
Total time: 15.931 secs
And, when running the "java -version" command from the command line, I get
the following:
D:\temp>java -version
java version "1.6.0_17"
Java(TM) SE Runtime Environment (build 1.6.0_17-b04)
Java HotSpot(TM) Client VM (build 14.3-b01, mixed mode, sharing)
So, I'm using the same JDK, with the only difference being 32-bit on the
Windows machine, and 64-bit on the Fedora machine. These were both executed
with a clone of the git repository as of about 10:00 EST today.
In searching the archives, the only thing I could find that I thought might
even be related was GRADLE-1252, which refers to TestNG output.
Does anyone have any ideas on this?
Thanks!
-=b=-
Bill Carlson
