[MNG-7122] Require specific Maven compatibility version for plugins
- Dominant language
- Java
- Stars
- 5.3k
- Forks
- 3.1k
- Avg merge
- 20h 42m
- Merged PRs (30d)
- 297
Description
**[Robert Scholte](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rfscholte)** opened **[MNG-7122](https://issues.apache.org/jira/browse/MNG-7122?redirect=false)** and commented
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.
---
**Issue Links:**
- [MNG-7020](https://issues.apache.org/jira/browse/MNG-7020) Remove Maven 2 WagonExcluder backward compat code
(_**"blocks"**_)
1 votes, 5 watchers
Contributor guide
Assessment
This issue has not been assessed yet.