• Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major Major
    • envinject-plugin
    • 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.

          [JENKINS-21285] Remove Maven Plugin dependency

          Owen Mehegan added a comment -

          Looks like this was fixed at some point.

          Owen Mehegan added a comment - Looks like this was fixed at some point.

            gbois Gregory Boissinot
            danielbeck Daniel Beck
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: