-
Improvement
-
Resolution: Fixed
-
Trivial
-
None
-
Jenkins 1.476
Warnings 4.13
Red Hat Enterprise Linux 5.5 64 bit
Sun Java 1.6.0_20
-
-
warnings-ng 1.0.0-beta1
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)
- depends on
-
JENKINS-44957 Remove maven project dependency
-
- Resolved
-
Code changed in jenkins
User: Ulli Hafner
Path:
plugin/pom.xml
http://jenkins-ci.org/commit/findbugs-plugin/cf1aeabc68913d1d4dbeb9d050d7d85fb6d8781e
Log:
JENKINS-21268JENKINS-14727Make maven-plugin a mandatory dependency.Workaround for
JENKINS-21268. The maven plug-in can't be optional without breaking the API. This issue needs to be adressed in 2.x release.