Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Duplicate
-
Affects Version/s: 2.0.1
-
Fix Version/s: None
-
Component/s: Plugins and Lifecycle
-
Labels:None
-
Complexity:Expert
-
Number of attachments :
Description
plugin containers are only initialized once per build, which means they may contain incorrect project-introduced dependencies for project Y in a multimodule build (polluted by project X predecessor). We should look at ways of dumping plugin containers with project-specific configurations, or else providing a container overlay to handle project-specific dependencies, etc.
NOTE: This is tied into the notions of build extensions, which will have similar consequences on the core container.
Issue Links
| This issue duplicates: | ||||
| MNG-1323 | Plugin extensions (dependencies) not resolved in reactor build |
|
|
|
| This issue is duplicated by: | ||||
| MNG-1836 | inherited plugin dependencies |
|
|
|
| This issue relates to: | ||||
| MNG-1323 | Plugin extensions (dependencies) not resolved in reactor build |
|
|
|
| This issue is related to: | ||||
| MNG-1024 | Reactor does not allow multiple plugin versions across projects |
|
|
|
is this still an issue on trunk?