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

Make dependency to bundled maven-plugin optional

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved (View Workflow)
    • Priority: Trivial
    • Resolution: Fixed
    • Component/s: analysis-core-plugin, warnings-plugin
    • Labels:
      None
    • Environment:
      Jenkins 1.476
      Warnings 4.13
      Red Hat Enterprise Linux 5.5 64 bit
      Sun Java 1.6.0_20
    • Similar Issues:
    • Released As:
      warnings-ng 1.0.0-beta1

      Description

      Make dependency from warnings to (bundled) maven-plugin optional.
      [The maven-plugin also brings an indirect dependency to javadoc]

      We don't use Maven or Java in our Jenkins. All other bundled plugins were removed from jenkins.war (purpose: keep '/pluginManager/installed' UI list shorter, save some disk space)

        Attachments

          Issue Links

          depends on

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-44957 Remove maven project dependency

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

            Activity

              People

              Assignee:
              drulli Ulli Hafner
              Reporter:
              bgolding Ben Golding
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: