JDK installation influences already installed java instances, reinstall of Java had to be done to get back up and running

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      We have migrated from Hudson to Jenkins. We decided to create a new buildmaster, since we also faced some issue with the old master.
      On the new master we defined only 1 JDK.
      All builds try to install the new JDK (1.6.23) and on a number of systems (windows) this gave an issue.

      The JDK gets installed in ../tools/1.6.23, but the public JRE get installed in C:\Program Files\Java\jre6
      That influences already installed Java installation(s).
      On a number of machine we had to remove all Java installation and do a manual installation again to get it back up and running.

      For windows the public JRE has to be skipped I think.
      That can be done with the following command: ADDLOCAL="ToolsFeature,DemosFeature,SourceFeature"
      Or the install directory of the public JRE has to be defined as well: /INSTALLDIRPUBJRE=...
      That is not done right now.

      More info: http://www.oracle.com/technetwork/java/javase/install-windows-189425.html

      This issue is very frustrating and causing a lot of issue and loss of time.

            Assignee:
            Unassigned
            Reporter:
            Cees Bos
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: