[
https://issues.apache.org/jira/browse/MNG-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17841181#comment-17841181
]
Juul Hobert commented on MNG-7122:
----------------------------------
#MNG-7754 already reports when a Maven 2.x dependency is used in a plugin. Does
this ticket still describe useful functionality? It looks to me that MNG-7754
already covers enough so that the described functionality in this ticket is not
useful anymore. [~rfscholte] and [~cstamas] can you give your vision on this?
> Require specific Maven compatibility version for plugins
> --------------------------------------------------------
>
> Key: MNG-7122
> URL: https://issues.apache.org/jira/browse/MNG-7122
> Project: Maven
> Issue Type: New Feature
> Components: Plugins and Lifecycle
> Reporter: Robert Scholte
> Assignee: Robert Scholte
> Priority: Major
> Fix For: 4.0.x-candidate
>
>
> By removing the WagonExcluder (MNG-7020) it could mean that plugins that rely
> on Maven2 dependencies might leak an old wagon-version onto the classpath.
> Plugins can already define a prerequisite for the Maven version, but we also
> need a mechanism to do it the other way around: plugins should at least
> require maven dependencies of version x.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)