[MNG-2180] Allow aggregation mojos to access plugin configurations

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Incomplete
• Affects Version/s: 2.0.3
• Component/s: Plugin API
• Assignee: Unassigned
• Reporter: Vincent Massol
• Created: 27/Mar/06 01:30
• Updated: 31/Dec/23 10:43
• Resolved: 22/Jan/14 20:31

Description

Here's my use case:

• I'm writing an aggregated report for the clover plugin. It needs to locate all children's clover databases and merge them into a single one and then generate a report out of it
• The location of the Clover databases is stored in plugin's configuration
• The problem is that I cannot access a plugin configuration using the plugin API

This is a general problem. By definition any aggregation mojo needs to access configuration information from its children. Some time out of sheer luck the information the plugin needs is found in the general section of the POM. However this is very limited and forbids any use case where the configuration is stored in <plugin><configuration>.

Issue Links

• is related to: MNG-7991 refactor "aggregator" goal feature
• relates to: MNG-250 make aggregation feasible