Details
-
Type:
Improvement
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Won't Fix
-
Component/s: m2release-plugin, maven-plugin, plugin-proposals, release-plugin
-
Labels:None
-
Similar Issues:
Description
I found out that there are 2 Jenkins Plugins which have nearly the same name.
( https://wiki.jenkins-ci.org/display/JENKINS/Release+Plugin &
https://wiki.jenkins-ci.org/display/JENKINS/M2+Release+Plugin )
And both of them are very useful! But I wanted to ask why they don't fit together?
Because I really like the feature of the "Release Plugin" to be able to define build steps before maven releases are triggered. But obviously these pre/past build actions won't be triggered if you use the "M2 Release Plugin" for executing the release.
Would be great if the two Plugins work together and kind of "know each other"!
Attachments
Activity
also the feature to automatically load the next versions and suggest them in the version fields I am missing in the "Release Plugin" whereas the "M2 Release Plugin" does a great job here.
Or do the two Plugins disturb each other when parallel installed??
The 2 plugins do different things - m2release is for releasing maven projects using the maven release plugin. The release plugin is for wrapping arbitrary pre and post build steps around freestyle of maven based jobs. I don't think merging these two would add much value.