You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Vincent Massol (JIRA)" <ji...@codehaus.org> on 2006/03/27 09:32:14 UTC
[jira] Created: (MNG-2180) Allow aggregation mojos to access plugin
configurations
Allow aggregation mojos to access plugin configurations
-------------------------------------------------------
Key: MNG-2180
URL: http://jira.codehaus.org/browse/MNG-2180
Project: Maven 2
Type: Improvement
Components: Plugin API
Versions: 2.0.3
Reporter: Vincent Massol
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>.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (MNG-2180) Allow aggregation mojos to access plugin
configurations
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2180?page=all ]
John Casey updated MNG-2180:
----------------------------
Fix Version: 2.1
> Allow aggregation mojos to access plugin configurations
> -------------------------------------------------------
>
> Key: MNG-2180
> URL: http://jira.codehaus.org/browse/MNG-2180
> Project: Maven 2
> Type: Improvement
> Components: Plugin API
> Versions: 2.0.3
> Reporter: Vincent Massol
> Fix For: 2.1
>
>
> 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>.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (MNG-2180) Allow aggregation mojos to access
plugin configurations
Posted by "Milos Kleint (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2180?page=comments#action_62134 ]
Milos Kleint commented on MNG-2180:
-----------------------------------
another usecase is the IDE integration where I need to check the location of generated sources for example. or I need to figure out the version of the javac that is used by the compiler plugin..etc..
> Allow aggregation mojos to access plugin configurations
> -------------------------------------------------------
>
> Key: MNG-2180
> URL: http://jira.codehaus.org/browse/MNG-2180
> Project: Maven 2
> Type: Improvement
> Components: Plugin API
> Versions: 2.0.3
> Reporter: Vincent Massol
>
>
> 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>.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira