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

If an m2 module is automatically disabled, it cannot be re-enabled

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • maven-plugin
    • None
    • Platform: All, OS: All

      If a submodule of an m2 project is dereferenced, Hudson (very usefully) disables
      the corresponding module job. However if the submodule is readded later, Hudson
      does not re-enable the module job.

      To be more concrete: say you have a POM with modules like so

      <modules>
      <module>foo</module>
      <module>bar</module>
      </modules>

      If you were to remove "bar", Hudson would stop building the corresponding
      artifact. If you added "bar" back later (without changing the group/artifact
      ID), Hudson behaves as though it didn't notice.

      A workaround is to edit the config.xml for the previously disabled module and
      remove the <disabled>true</disabled> element, then tell Hudson to reread the
      configuration from disk.

          [JENKINS-569] If an m2 module is automatically disabled, it cannot be re-enabled

          rsutphin created issue -

          Fixed in 1.109.

          Kohsuke Kawaguchi added a comment - Fixed in 1.109.
          Kohsuke Kawaguchi made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          Andrew Bayer made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]
          Jenkins IRC Bot made changes -
          Component/s New: maven-plugin [ 16033 ]
          Component/s Original: maven2 [ 15487 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 130642 ] New: JNJira + In-Review [ 199994 ]

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

              Created:
              Updated:
              Resolved: