[MNG-2893] Update the DefaultPluginManager to not use a project depMan for controlling its transitive dependencies
Open
maintenance
priority:major
- Dominant language
- Java
- Stars
- 5.3k
- Forks
- 3.1k
- Avg merge
- 20h 40m
- Merged PRs (30d)
- 275
Description
**[Jason van Zyl](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jvanzyl)** opened **[MNG-2893](https://issues.apache.org/jira/browse/MNG-2893?redirect=false)** and commented
An adjustment to MNG-1577. The classpath for plugins should not be affected by a projects depMan.
---
**Affects:** 2.0.5
**Issue Links:**
- [MNG-8559](https://issues.apache.org/jira/browse/MNG-8559) Rewrite DefaultPluginManager with Maven 4 API
(_**"Is contained by"**_)
**Remote Links:**
- [GitHub Pull Request #144
](https://github.com/apache/maven/pull/144)
**Backported to:** [3.2.x](https://github.com/apache/maven/milestone/82?closed=1)
1 votes, 4 watchers
Contributor guide
Assessment
This issue has not been assessed yet.