Bugs item #1010214, was opened at 2004-08-16 18:40
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=438935&aid=1010214&group_id=44253
Category: Debugger
Group: Annoying
Status: Open
Resolution: None
Priority: 5
Submitted By: Jonathan Lugo (jeloguy15)
Assigned to: Jonathan Lugo (jeloguy15)
Summary: Error displayed on startup even if compiler was found
Initial Comment:
Story:
The user has 2 versions of the SDK installed on their
computer at the same time (e.g. j2sdk1.4.2 & jdk1.5.0).
Java 1.5 is the default JVM (either because of the
$JAVA_HOME variable in Linux/Unix, or because it was
the last one installed in Windows), but the user runds
DrJava in the other one (i.e. j2sdk1.4.2).
When DrJava starts up it says that it couldn't find a
valid tools.jar. Even when the user selects the
correct toos.jar, it again warns that this version is
incompatible.
When the user has no choice but select 'No', the
correct compilers still show up in the compilers menu
making the message seem unnecessary.
Problem:
The same message is displayed when EITHER the compiler
OR the debugger cannot be loaded correctly. So if the
compiler loads well but the debugger doesn't, the user
will still think drjava cannot find the compiler.
Partial Solution:
I created two error messages: one if the compiler fails
and one if the debugger fails. These messages explain
more accurately what's going on.
** I'm leaving this bug open because I think we should
look into why the debugger isn't loading when the
correct tools.jar is given.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=438935&aid=1010214&group_id=44253
|
