• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • other
    • None
    • Platform: All, OS: All

      I have Hudson 1.213 and it does not run on IBM WAS 6.1 again. Version 1.197
      works for me.

          [JENKINS-1680] Hudson does not run on IBM WebSphere 6.1

          shamoh added a comment -

          Created an attachment (id=248)
          WAS' SystemOut.log

          shamoh added a comment - Created an attachment (id=248) WAS' SystemOut.log

          Can anyone dig a little deeper and find out which class is causing
          java.lang.IncompatibleClassChangeError?

          It looks like the error message is missing the crucial information.

          Kohsuke Kawaguchi added a comment - Can anyone dig a little deeper and find out which class is causing java.lang.IncompatibleClassChangeError? It looks like the error message is missing the crucial information.

          Recent thread in the users list:
          http://www.nabble.com/Issue-1680-td18383889.html

          Kohsuke Kawaguchi added a comment - Recent thread in the users list: http://www.nabble.com/Issue-1680-td18383889.html

          Code changed in hudson
          User: : kohsuke
          Path:
          trunk/hudson/main/core/pom.xml
          trunk/www/changelog.html
          http://fisheye4.cenqua.com/changelog/hudson/?cs=10817
          Log:
          [FIXED JENKINS-1680]
          Patched jtidy locally to make Hudson work in WebSphere once again.
          See http://www.nabble.com/Issue-1680-td18383889.html

          SCM/JIRA link daemon added a comment - Code changed in hudson User: : kohsuke Path: trunk/hudson/main/core/pom.xml trunk/www/changelog.html http://fisheye4.cenqua.com/changelog/hudson/?cs=10817 Log: [FIXED JENKINS-1680] Patched jtidy locally to make Hudson work in WebSphere once again. See http://www.nabble.com/Issue-1680-td18383889.html

            Unassigned Unassigned
            shamoh shamoh
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: