Issue Type: Improvement Improvement
Assignee: Gregory Boissinot
Components: envinject
Created: 08/Jan/14 7:55 PM
Description:

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.

Project: Jenkins
Priority: Major Major
Reporter: Daniel Beck
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to