-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P4
-
Affects Version/s: None
-
Component/s: infrastructure
-
None
-
b28
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8056317 | emb-9 | Erik Joelsson | P4 | Resolved | Fixed | b28 |
I used to be able to build JDK 9 on ja_JP.UTF-8 locale, but build process recently started failing.
Generated .java files in build/.../corba/gensrc/com/sun/corba/se/spi/activation/ contain some
localized comments, and they started causing compilation errors.
Using C locale to build JDK is clearly mentioned in jdk/make/netbeans/README. But if it is a mandatory requirement, it should be mentioned in README-builds.html in the top directory of JDK workspace.
This is reproducible on Linux and MacOS. I haven't tried on other platforms nor other non-English locales.
Generated .java files in build/.../corba/gensrc/com/sun/corba/se/spi/activation/ contain some
localized comments, and they started causing compilation errors.
Using C locale to build JDK is clearly mentioned in jdk/make/netbeans/README. But if it is a mandatory requirement, it should be mentioned in README-builds.html in the top directory of JDK workspace.
This is reproducible on Linux and MacOS. I haven't tried on other platforms nor other non-English locales.
- backported by
-
JDK-8056317 JDK 9 build started failing on ja_JP.UTF-8 locale due to mapping error (encoding=ascii).
-
- Resolved
-
- relates to
-
-
- Resolved
-