|
[
Permalink
| « Hide
]
md added a comment - 21/Nov/07 03:50 PM
I would appreciate it if this gets a "Critical" priority. My usage is related to being able to specify custorm PMD rules in an external jar that I need to be in the classpath for the maven-pmd-plugin. This is a serious deficiency and is requiring us to use cumbersome workarounds and potentially making our builds brittle
I think it would be a real good improvement and it's really a need. For instance for all report plugin with custom rules.
That will save using bad design like extensions as described in MPMD-22 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 nm, guess this'll have to wait.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Improvement
Open
Major
reporting section should allow additional dependencies in plugins as well
