Review request: 8004658: Add internal smart javac wrapper to solve JEP 139 (original) (raw)
Jonathan Gibbons jonathan.gibbons at oracle.com
Mon Jan 14 08:44:23 PST 2013
- Previous message: Review request: 8004658: Add internal smart javac wrapper to solve JEP 139
- Next message: Review request: 8004658: Add internal smart javac wrapper to solve JEP 139
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 01/14/2013 06:39 AM, Fredrik Öhrström wrote:
Because I do not want the stream from stderr/stdout to be piped back to the Java program that created the ProcessBuilder. I need to have stdout/stderr to end up on disk when the sjavac client terminates. I cannot see that ProcessBuilder has this feature. Please correct me if I am wrong.
Isn't easy enough to suck the output from the Process and write it to a file in the driving program? Why is it important to have the output written directly to disk?
If you want the output to be written directly to disk, do it within the exec-ed program.
Either way you should not need to go through an intermediate layer of shell.
-- Jon
- Previous message: Review request: 8004658: Add internal smart javac wrapper to solve JEP 139
- Next message: Review request: 8004658: Add internal smart javac wrapper to solve JEP 139
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]