-
Epic
-
Resolution: Fixed
-
Minor
-
Break transitive dependencies on maven-integration-plugin
-
We would like people to stop using https://wiki.jenkins.io/display/JENKINS/Maven+Project+Plugin but the user base is still growing (less quickly fortunately).
I think one of the main contributors to this is that it is actually impossible today to not install that plugin. It's pulled in by basically the whole world.
So for instance, even if it's not explicitly in the Jenkins 2 installation wizard list of plugins, it will always be installed transitively.
Then, imagine a newcomer installing Jenkins for the first time for a try, using Maven and Java on a daily basis... Installed Jenkins, clicked "New Item", who is not going to click on "Maven Job"?...
So if we ever to move forward and see the usage of this plugin decrease significantly, we need in my opinion to first work so that it is not automatically installed on every single Jenkins instance in the world...
[JENKINS-46684] Break transitive dependencies on maven-integration-plugin
| Description |
Original:
We would like people to stop using https://wiki.jenkins.io/display/JENKINS/Maven+Project+Plugin but the user base is still growing (less quickly fortunately). I think one of the main contributors to this is that it is actually *impossible* today to not install that plugin. It's pulled in by basically the whole world. So for instance, even if it's not explicitly in the Jenkins 2 installation wizard list of plugins, it will always be installed transitively. Then, imagine a newcomer installing Jenkins for the first time for a try, using Maven and Java on a daily basis... Installed Jenkins, clicked "New Item", who is *not* going to click on "Maven Job"?... |
New:
We would like people to stop using https://wiki.jenkins.io/display/JENKINS/Maven+Project+Plugin but the user base is still growing (less quickly fortunately). I think one of the main contributors to this is that it is actually *impossible* today to not install that plugin. It's pulled in by basically the whole world. So for instance, even if it's not explicitly in the Jenkins 2 installation wizard list of plugins, it will always be installed transitively. Then, imagine a newcomer installing Jenkins for the first time for a try, using Maven and Java on a daily basis... Installed Jenkins, clicked "New Item", who is *not* going to click on "Maven Job"?... So if we ever to move forward and see the usage of this plugin decrease significantly, we need in my opinion to first work so that it is *not* automatically installed on every single Jenkins instance in the world... |
| Component/s | New: maven-plugin [ 16033 ] | |
| Component/s | Original: _unsorted [ 19622 ] |
| Assignee | Original: Oleg Nenashev [ oleg_nenashev ] |
| Assignee | New: Arnaud Héritier [ aheritier ] |
I think batmat should provide a list of plugins to be modified for starters. Maven plugin may need some API tweaks to support detaching (like jglick did for matrix), but this EPIC is not ready for implementation. Assigning to Baptiste
| Assignee | Original: Arnaud Héritier [ aheritier ] | New: Baptiste Mathus [ batmat ] |
Assigned to Maven Plugin Maintainers.
IMHO Jenkins admins should be just able to enable/disable job types in the core, e.g. via https://wiki.jenkins.io/display/JENKINS/Extension+Filter+Plugin