JDK-8193784 : Support javac --release 11
  • Type: Sub-task
  • Component: tools
  • Sub-Component: javac
  • Affected Version: 11
  • Priority: P2
  • Status: Resolved
  • Resolution: Duplicate
  • Submitted: 2017-12-19
  • Updated: 2018-05-17
  • Resolved: 2018-05-14
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.
JDK 11
11Resolved
Related Reports
Blocks :  
JDK-8196619 - [TESTBUG] restore current version check in runtime/appcds/MultiReleaseJars.java
Duplicate :  
JDK-8202387 - javac --release 11 not supported
Relates :  
JDK-8193291 - Add SourceVersion.RELEASE_11
Relates :  
JDK-8173382 - Add -source 11 and -target 11 to javac
Description
As part of starting JDK 11, support should be added for

    javac --release 11
Comments
Resolved under JDK-8202387.
14-05-2018
We need to revise the policy so that javac support for "--release N" is available out of the box for JDK N. This is easily automated for N, either in the Makefiles or by enhancing the build tools. The more tricky aspect, which is not automatable, is to ensure that support for "--release N-1" is made available soon after we update N. This requires generating the history files for N-1 and checking them into the repo. A short-term interim solution is to make N-1 be effectively be an alias for N until the history files are available. Note this is somewhat complicated by the six-month release cadence, since we start working on N before N-1 is final.
01-05-2018
The test langtools/tools/javac/modules/JavaBaseTest.java would also be impacted by the lack of support for --release 11 once the version update occurs.
01-02-2018
Note that there are two tests on the langtools ProblemList.txt file for this issue.
19-12-2017