-
Bug
-
Resolution: Fixed
-
P1
-
9
-
b177
-
Not verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8184002 | 10 | Kumar Srinivasan | P1 | Resolved | Fixed | b15 |
JDK-8183410 | 9.0.4 | Kumar Srinivasan | P1 | Resolved | Fixed | b01 |
This issue was reported on jdk9-dev here:
http://mail.openjdk.java.net/pipermail/jdk9-dev/2017-June/005900.html
The --permit-illegal-access option in the JDK 9 EA builds was replaced by --illegal-access=<value> in jdk-9+175. This missed the final translation drop so now we have `java -help` printing wrong output when on non-English systems.
Minimally we need to change the non-English launcher.properties files to remove the lines for --permit-illegal-access and avoid confusing developers. It's not critical that the translations document --illegal-access.
http://mail.openjdk.java.net/pipermail/jdk9-dev/2017-June/005900.html
The --permit-illegal-access option in the JDK 9 EA builds was replaced by --illegal-access=<value> in jdk-9+175. This missed the final translation drop so now we have `java -help` printing wrong output when on non-English systems.
Minimally we need to change the non-English launcher.properties files to remove the lines for --permit-illegal-access and avoid confusing developers. It's not critical that the translations document --illegal-access.
- backported by
-
JDK-8183410 java --help-extra in non-English locales lists --permit-illegal-access which no longer exists
-
- Resolved
-
-
JDK-8184002 java --help-extra in non-English locales lists --permit-illegal-access which no longer exists
-
- Resolved
-
- relates to
-
JDK-8183579 refactor and cleanup launcher help messages
-
- Open
-