[DrJava] [ drjava-Bugs-529053 ] check on "bad" compilers not working

[<no...@so...>]

Bugs item #529053, was opened at 2002-03-12 12:25
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=438935&aid=529053&group_id=44253

Category: User interface
Group: Annoying
Status: Open
Resolution: None
Priority: 7
Submitted By: Eric E. Allen (eallen)
Assigned to: Brian Stoler (brianstoler)
Summary: check on "bad" compilers not working

Initial Comment:
When DrJava is started from a jar (with a JDK _or_ a 
JRE), with a .drjava file that contains no entry for 
javac.location, the user will always get a "Compiler 
not found" dialog. This shouldn't happen when using a 
JDK.

More seriously, if, when using a JDK, the user 
specifies an inappropriate compiler (e.g., bin/javac) 
DrJava will not issue a warning. In fact, there will 
be an active compiler registered! But when the user 
starts up DrJava again, the same "Compiler not found" 
dialog will come up.

I suspect that the problem is as follows: 

The decision to bring up the "Compiler not found" 
dialog is done before DrJava detects the compiler 
from the JDK. This compiler is then found during the 
process of registering the user-specified compiler. 
If the user-specified compiler is wrong, DrJava only 
notices that _some_ compiler has been registered 
successfully, and assumes it's the one specified by 
the user. But when DrJava is started again, it 
recognizes that javac.location in the .drjava file is 
inappropriate, so the same process happens all over 
again.

-- Eric


----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=438935&aid=529053&group_id=44253