P3
$ java -version
java version "1.4.0-beta_refresh"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-beta_refresh-b72)
Java HotSpot(TM) Client VM (build 1.4.0-beta_refresh-b72, mixed mode)
$ javac -encoding foo Test.java
error: compiler message file broken: key=compiler.err.java.io.UnsupportedEncodingException: foo arguments=null, null, null, null, null, null, null
1 error
It looks like getLocalizedString(String key) is being called with the name of
the thrown exception rather than a valid key (which doesn't appear to exist in
the resource bundle).
In jdk1.3, this was similarly broken. In jdk1.2, the compiler silently ignores
the invalid encoding and produces a .class file, presumably using the machine's
default encoding.
- iag@eng 2001-07-23
java version "1.4.0-beta_refresh"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-beta_refresh-b72)
Java HotSpot(TM) Client VM (build 1.4.0-beta_refresh-b72, mixed mode)
$ javac -encoding foo Test.java
error: compiler message file broken: key=compiler.err.java.io.UnsupportedEncodingException: foo arguments=null, null, null, null, null, null, null
1 error
It looks like getLocalizedString(String key) is being called with the name of
the thrown exception rather than a valid key (which doesn't appear to exist in
the resource bundle).
In jdk1.3, this was similarly broken. In jdk1.2, the compiler silently ignores
the invalid encoding and produces a .class file, presumably using the machine's
default encoding.
- iag@eng 2001-07-23