[
http://jira.codehaus.org/browse/MNG-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=173928#action_173928
]
John Casey commented on MNG-1948:
---------------------------------
One thing we could fix for the near term is allowing reporting plugins to use
information from the pluginManagement section, including dependencies. While
it's a model change that would require a bump to modelVersion if we put in
report-plugin-level dependencies, we can make this work with the
DefaultPluginManager today, and we certainly should be supplying defaults like
version, etc. from pluginManagement to the report plugins anyway.
I'd like to tackle this for 2.1.1. It's a fairly straightforward workaround,
and would lessen the side-effect problems that people run into like MNG-4140.
> reporting section should allow additional dependencies in plugins as well
> -------------------------------------------------------------------------
>
> Key: MNG-1948
> URL: http://jira.codehaus.org/browse/MNG-1948
> Project: Maven 2
> Issue Type: Improvement
> Components: Plugins and Lifecycle, POM
> Reporter: Brett Porter
> Fix For: 2.1.1, 3.x
>
>
> currently, you can only do this in the build section
--
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
