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

Allow user to not overwrite existing VM when installing on windows.

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Won't Fix
    • Icon: P4 P4
    • None
    • jaws-1.0
    • deploy
    • x86
    • generic

      feedback request from:
      "Adam Shackleford" <###@###.###>
      -----------------------
      >Installing JWS 1.0 RC replaces your system's VM (the "java" command at the
      >command line) with Sun's JRE 1.3.0. That's very rude, not to mention
      >Sun-centric.
      > 1.. I installed IBM's JRE 1.3.0-service-release-2. I used it for several
      >days--it ran fine.
      > 2.. I installed JWS 1.0 RC.
      > 3.. I ran my Java application from the command line and noticed it
      >misbehaving (Sun's JRE 1.3.0 has bug 4336459; IBM's does not).
      > 4.. The "java -version" command revealed that the JWS install had hammered
      >IBM's JRE and replaced it with Sun's JRE 1.3.0.
      >Please fix this. JWS should have exactly zero coupling to the "java"
      >command:
      > a.. Under no circumstances should JWS tamper with the system's default VM.
      > b.. JWS should *always always always* install Sun's JRE. Developers are
      >looking for certainty from JWS, not the "JVM of the day". The existing JVM
      >may be damaged, or it may have bugs. When I ask my users to install JWS, I
      >want to *know* absolutely what JRE is available for my app. JWS wants to be
      >utterly decoupled from everything but the underlying OS.
      >thanks,
      --------------------

            sbohne Steve Bohne (Inactive)
            herrick Andy Herrick (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: