Bugs item #686849, was opened at 2003-02-14 23:25
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=438935&aid=686849&group_id=44253
Category: Compiler integration
Group: Serious
Status: Open
Resolution: None
Priority: 9
Submitted By: Charles Reis (csreis)
Assigned to: Charles Reis (csreis)
Summary: Can't use JSR-14 with latest dev release (20030209)
Initial Comment:
It appears that you cannot use the JSR-14 compiler
within the drjava-20020309-2341 development release.
If you put *anything* in the JSR-14 Location option in
the preferences, it will recognize it as JSR-14 (v1.2
if you are running JDK 1.4.1 and v1.0 otherwise), but
it cannot compile any code with generics.
This is likely a result of forcing tools.jar onto the
classpath (which we now do to get access to the
debugger). The compiler adapters see a copy of
com.sun.tools.javac.v8.JavaCompiler in tools.jar and
mistake it for JSR-14.
Wow! This is even worse than I thought, and I can't
believe it hasn't been noticed before! It seems we
have this problem in all of our old versions of DrJava
as well, if you go to the trouble to use the debugger.
If you put tools.jar on the classpath along with the
DrJava jar file, you will not be able to use JSR-14.
(It loads the classes from tools.jar instead of the
specified jsr14.jar.)
This is serious, and will likely involve changes to how
the compiler classes are loaded. It is essential that
we can compile with JSR-14, and we need tools.jar to be
able to use the debugger. These cannot be mutually
exclusive features...
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=438935&aid=686849&group_id=44253
|
