• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • core
    • None
    • Oracle JRockit build R28.0.0

      Same issue was raised in XStream's JIRA (please see the attached URL).

      s from version 4.0.0, Oracle changed the Vendor name of it's JVM, Oracle JRockit. Until this point the Vendor name was "BEA" - this is for what the current 1.3.1 XStream implementation looks for while checking JVM vendors. Oracle changed this in this release to "Oracle" which now causes to fail the vendor check in XStream.

      The result of this bug is that hudson starts, but instead of the welcome screen, it only shows a page that complains about XStream is not supporting this VM.

          [JENKINS-6556] XStream-bug: JRockit JVM Vendor change

          Alan Harder added a comment -

          Alan Harder added a comment - Do you think this will work? http://github.com/hudson/xstream/commit/0f375be9918eef6627912fca1a4ac72fa83aca28

          sandor_nemeth added a comment -

          Yes, I think this would do the trick.

          Thank you for the quick response!

          Regards,
          Sandor Nemeth

          sandor_nemeth added a comment - Yes, I think this would do the trick. Thank you for the quick response! Regards, Sandor Nemeth

          Code changed in hudson
          User: : mindless
          Path:
          trunk/hudson/main/core/pom.xml
          trunk/www/changelog.html
          http://jenkins-ci.org/commit/31175
          Log:
          [FIXED JENKINS-6556] bump to xstream-1.3.1-hudson-7,
          to accept latest JRockit JVM release as a compatible JVM.

          SCM/JIRA link daemon added a comment - Code changed in hudson User: : mindless Path: trunk/hudson/main/core/pom.xml trunk/www/changelog.html http://jenkins-ci.org/commit/31175 Log: [FIXED JENKINS-6556] bump to xstream-1.3.1-hudson-7, to accept latest JRockit JVM release as a compatible JVM.

            mindless Alan Harder
            sandor_nemeth sandor_nemeth
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: