Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-12583

update for cvs plugin to 2.0 doesn't work

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Postponed
    • Icon: Major Major
    • core, cvs-plugin
    • None
    • jenkins 1.449, cvs plugin 1.6

      I tried to update to the cvs plugin 2.0 today but this doesn't work, I assume there is a name problem due to the extension *.jpi on the new plugin.
      Before update, the file is called cvs.hpi, the update process creates a new file cvs.jpi that is ignored with the following message:

      Jan 30, 2012 5:04:26 PM hudson.PluginManager$1$3$1 isDuplicate
      INFO: Ignoring /home/lehmann/.jenkins/plugins/cvs.jpi because /home/lehmann/.jenkins/plugins/cvs.hpi is already loaded

      I assume it may work if it were the other way around.

      The version displayed by the plugin page remains 1.6 but there are a few exceptions in the log about missing classes like this

      java.lang.NoClassDefFoundError: org/netbeans/lib/cvsclient/admin/AdminHandler

      these classes are included in the cvs.jpi zip but that is not used.

      I was able to fix the update manually by copying cvs.jpi to cvs.hpi, which resulted in a pinned plugin 2.0, but the automatic process has to be fixed somehow.

          [JENKINS-12583] update for cvs plugin to 2.0 doesn't work

          Alex Lehmann created issue -

          stibbons added a comment -

          I do have the same issue with this upgrade. Thanks for the fix, it worked. Thanks.

          stibbons added a comment - I do have the same issue with this upgrade. Thanks for the fix, it worked. Thanks.

          Michael Clarke added a comment -

          I don't think this is directly related to the CVS plugin, but rather to a change in the way the core handles plugins (it's doing the change from .hpi to .jpi) as I've seen others complain about a similar issue with different plugins. I'll see if I can find out more, but it's likely this needs a change to Core.

          Michael Clarke added a comment - I don't think this is directly related to the CVS plugin, but rather to a change in the way the core handles plugins (it's doing the change from .hpi to .jpi) as I've seen others complain about a similar issue with different plugins. I'll see if I can find out more, but it's likely this needs a change to Core.

          Michael Clarke added a comment - - edited

          A fix has been applied to Jenkins core for version 1.450 which should resolve this issue

          Michael Clarke added a comment - - edited A fix has been applied to Jenkins core for version 1.450 which should resolve this issue
          Michael Clarke made changes -
          Link New: This issue depends on JENKINS-12514 [ JENKINS-12514 ]

          Fred G added a comment -

          Update worked fine with Jenkins version 1.447.

          @Michael Clarke: I guess you meant version 1.450.

          Fred G added a comment - Update worked fine with Jenkins version 1.447. @Michael Clarke: I guess you meant version 1.450.

          Michael Clarke added a comment -

          I did mean 1.450 (I've fixed the comment). Given this is a known issue in core and has been fixed, I'm marking this issue as resolved

          Michael Clarke added a comment - I did mean 1.450 (I've fixed the comment). Given this is a known issue in core and has been fixed, I'm marking this issue as resolved

          Michael Clarke added a comment -

          Fixed by a change to the core for version 1.450 as per linked defect

          Michael Clarke added a comment - Fixed by a change to the core for version 1.450 as per linked defect
          Michael Clarke made changes -
          Fix Version/s New: current [ 10162 ]
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

          Alex Lehmann added a comment -

          I noticed the same problem on the subversion plugin now, I should have checked that beforehand.

          Alex Lehmann added a comment - I noticed the same problem on the subversion plugin now, I should have checked that beforehand.

            alexlehm Alex Lehmann
            alexlehm Alex Lehmann
            Votes:
            3 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: