Bug ID: JDK-4087072 eou: Development tools not 100% pure

Type: Bug
Component: tools
Sub-Component: launcher
Affected Version: 1.1,1.1.3,1.2.0,1.2.1

Priority: P5
Status: Closed
Resolution: Duplicate
OS: generic,solaris_2.5.1
CPU: generic,sparc

Submitted: 1997-10-17
Updated: 2001-07-13
Resolved: 2001-07-13


Name: joT67522			Date: 10/17/97


Java development tools such as javac cannot be
integrated into a 100% Pure Java development 
environment because they call System.exit(), 
which, according to the API, "Terminates the
currently running Java Virtual Machine."

There is no compelling technical reason for these
tools to use System.exit(), and the fact that they
do so undermines the possibility of doing real
work within the confines of the Java sandbox.


company - Global One Telecommunications (Beijing) Co. Ltd. , email - ###@###.###
======================================================================

SUGGESTED FIX Name: joT67522 Date: 10/17/97 Return from main(). ======================================================================

11-06-2004

PUBLIC COMMENTS ..

10-06-2004

EVALUATION This is an extermely reasonable request. There are two significant problems: 1) There are alot of calls to exit() in java tools. 2) Much more importantly, tools need to be able to return an exit status, I know of no other way to do this but exit(). robert.field@Eng 1997-10-23 javac already encapsulates its Main into a little wrapper to allow the testing folks to avoid the System.exit() call. Other tools should do the same. It would make sense to go the extra mile and come up with a standard interface to our tools able to handle error messages and perhaps encapsulate context such as the CLASSPATH. It's even been suggested that our tools should become beans. david.stoutamire@Eng 1997-11-05

05-11-1997

Duplicate :	JDK-4060034 - RFE: Need a portable way to compile
Duplicate :	JDK-4164450 - JSR 199: Standard interface for Java compilers
Duplicate :	JDK-4065325 - Why not a class to represent the javac compiler ?