Issue Details (XML | Word | Printable)

Key: MNG-1949
Type: Bug Bug
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: John Casey
Votes: 14
Watchers: 7
Operations

If you were logged in you would be able to see more operations.
Maven 2

project-level plugin dependencies not handled correctly in multimodule builds

Created: 09/Jan/06 06:45 PM   Updated: 13/Dec/08 06:34 PM
Component/s: Plugins and Lifecycle
Affects Version/s: 2.0.1
Fix Version/s: 3.x

Time Tracking:
Not Specified

Issue Links:
Duplicate
Related

Complexity: Expert


 Description  « Hide
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.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Brett Porter added a comment - 07/Sep/07 12:26 AM
is this still an issue on trunk?

Piotr Tabor added a comment - 07/Sep/07 07:42 AM
Yes - it is still problem in trunk. JIRA for MNG-1323 contains patch for 2.0.x...
I am preparing patch for 2.1... I hope to have it this weekend.

Piotr Tabor added a comment - 16/Sep/07 12:07 PM
Patch for MNG-1323 commited in trunk by Jason van Zyl. As MNG-1323 is dupliacate for
this problem - this also should be resolved in trunk. To be tested by reported.

Patch for 2.0.x is ready to be commited in MNG-1323.