Review request: 8004658: Add internal smart javac wrapper to solve JEP 139

[Fredrik Öhrström]

2013/1/14 Jonathan Gibbons <jonathan.gibbons at oracle.com>:
> 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?

Because the driving program is going to exit. The spawned JavacServer
is to be running in the background.
The output from starting the background jvm is important, since it can fail.

For example the new build system passes specific -Xmx and -Xms and
other settings to the javac server,
that are not necessary, or good when passed to the client. If these
are wrong, then the start
of the javac server jvm will fail, and if the output is not sent to
disk, then it will be impossible to see it.

> If you want the output to be written directly to disk, do it within
> the exec-ed program.

Not possible, since the actual start of the jvm can fail, which
happpens before the Java server
gets  a chance to start writing to disk.

//Fredrik