[
http://jira.codehaus.org/browse/MNG-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_101770
]
John Allen commented on MNG-2173:
---------------------------------
This has become a complete show stopper for us.
Is there no progress/thoughts/concern regarding this?
Many plugins require licenses and other auxiliary files and, this being maven
and about a reproducable build, we wanted to use the dependency system to
supply a JAR containing the license to a plugin via the Locator.java approach
(used by Clover, PMD and Checkstyle) supply the underlying tool API with the
JAR extracted resource.
BUT as reporting plugins cant have <dependencies> we were trying to use the
side effect of the fact (is this still a fact?) that if a plugin is already
configured and in the 'runtime scope' of the build (ie it was declared in the
<build><plugins> section of the POM but not bound to anything) then supposedly
the <reporting> plugin MOJO will use that previously configured plugin, and
thus find the <dependencies> defined in the
<build><plugins><plugin><dependencies> section when searching for resources in
it's configuration.
But it's not working and is causing me no end of frustration.
Can someone provide some forecasting as to whether this is
a) recognised as a serious omission from the model (that reporting plugins can
not have <dependencies>)
b) it has been scheduled for a fix
What else can we do in the meantime?
> support <dependencies> in <reporting> plugins
> ---------------------------------------------
>
> Key: MNG-2173
> URL: http://jira.codehaus.org/browse/MNG-2173
> Project: Maven 2
> Issue Type: Bug
> Components: Plugins and Lifecycle
> Reporter: John Allen
> Fix For: 2.1.x
>
>
> Inconsistency with rest of design.
--
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
