Name: rlT66838 Date: 02/15/2000


java version "1.3.0rc1"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0rc1-T)
Java HotSpot(TM) Client VM (build 1.3.0rc1-S, mixed mode)


In Java 1.2 developers could redirect compiler output to a file by typing
javac -J-Djavac.pipe.output=true MyClass.java > MyClass.err.

Additionally developers could redirect compiler output by typing java -Xstdout
MyClass.java > MyClass.err.

Both of these command lines would result in a file MyClass.err that contained
compiler output. Naturally, files of this nature are essential for locating
syntax errors and other compiler errors.

What can we do to regain this critical ability to capture compiler output on
Win32 platform?
(Review ID: 101261)
======================================================================

Name: rlT66838 Date: 02/17/2000


C:\java -version
java version "1.3.0rc1"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0rc1-T)
Java HotSpot(TM) Client VM (build 1.3.0rc1-S, mixed mode)



I have followed instructions in tech article 2089, which suggests using the
following line to redirect javac error messages to a file (necessary because
they scroll off scn):

2) compile using javac -J-Djavac.pipe.output=true myclass.java >outputfile


This does not work. would appreciate a workaround .thankyou
(Review ID: 101391)


Name: skT45625 Date: 08/02/2000


C:\>java -version
java version "1.3.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0-C)
Java HotSpot(TM) Client VM (build 1.3.0-C, mixed mode)

C:\>



Before JDK 2 version 1.3 you could set the compiler
property "javac.pipe.output" to true by using the following syntax:

javac -J-Djavac.pipe.output=true MyProg.java > errors.txt

However, this doesn't work with version 1.3. The setting has no effect.
(Review ID: 107880)
======================================================================