-
Improvement
-
Resolution: Fixed
-
Major
-
None
It makes no sense for a universal plugin like Envinject to have a mandatory Maven Integration plugin dependency.
We don't have Maven 2/3 jobs, I don't allow users to create Maven 2/3 jobs, yet I need the plugin for Envinject.
JENKINS-13167 should be solved in a way that allows that dependency to be removed or made optional.
- is related to
-
JENKINS-13167 Cannot use EnvInject in a Maven 2 Jenkins project
-
- Resolved
-
Looks like this was fixed at some point.