JDK-6374661 : JDI: Obsolete reference to java.compiler should be removed
  • Type: Bug
  • Component: core-svc
  • Sub-Component: debugger
  • Affected Version: 6
  • Priority: P5
  • Status: Closed
  • Resolution: Not an Issue
  • OS: generic
  • CPU: generic
  • Submitted: 2006-01-19
  • Updated: 2023-12-14
  • Resolved: 2016-11-04
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
tbdResolved
Related Reports
Relates :  
JDK-8304547 - Remove checking of -Djava.compiler in src/jdk.jdi/share/classes/com/sun/tools/jdi/SunCommandLineLauncher.java
Relates :  
JDK-5043991 - (spec) java.compiler related inconsistency between implementation and docs
Description
in SunCommandLineLauncher in JDK file src/share/classes/com/sun/tools/jdi/SunCommandLineLauncher.java there is a check of property "java.compiler" which is no longer attended to or otherwise supported by the JRE (except for some backward compatibility handling by the JVM). The presence of this reference just prolongs licensee uncertainty about the property status. And since "full speed debugging" was implemented a few releases back I don't think there has been a need to impose the restriction implied by this code in any case. So it should be OK to simply remove this:

        if ((options.indexOf("-Djava.compiler=") != -1) &&
            (options.toLowerCase().indexOf("-djava.compiler=none") == -1)) {
            throw new IllegalConnectorArgumentsException("Cannot debug with a JIT compiler",
                                                         ARG_OPTIONS);
        }
A comment to the effect that this functionality has no bearing on Sun's Java SE would help