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

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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: maven-plugin
    • Labels:
      None
    • Environment:
      Platform: All, OS: All
    • Similar Issues:

      Description

      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.

        Attachments

          Activity

            People

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

              Dates

              Created:
              Updated:
              Resolved: