Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-4483147

unexpected key compiler.err.java.io.UnsupportedEncodingException - bad encoding

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: P3
    • Resolution: Fixed
    • Affects Version/s: 1.4.0
    • Fix Version/s: 1.4.0
    • Component/s: tools
    • Labels:
    • Subcomponent:
    • Resolved In Build:
      beta3
    • CPU:
      generic
    • OS:
      generic
    • Verification:
      Verified

      Description

       $ 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

        Attachments

          Activity

            People

            Assignee:
            gafter Neal Gafter
            Reporter:
            iris Iris Clark
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: