Maven 2.x and 3.x Site Plugin

reporting section should allow additional dependencies in plugins as well

Details

  • Type: Improvement Improvement
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    0

Description

currently, you can only do this in the build section

Issue Links

This issue is duplicated by:
MNG-2173 support <dependencies> in <reporting> plugins Major Closed
This issue relates to:
MSITE-443 add a reportingManagement section Major Open
This issue is depended upon by:
MPMD-22 PMD plugin <configuration> should accept dependency entries Major Closed

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
md added a comment -

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

Show
md added a comment - 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
Hide
Permalink
Rémy Sanlaville added a comment -

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

Show
Rémy Sanlaville added a comment - 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
Hide
Permalink
John Casey added a comment - - edited

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-4074.

Show
John Casey added a comment - - edited 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-4074.
Hide
Permalink
John Casey added a comment -

nm, guess this'll have to wait.

Show
John Casey added a comment - nm, guess this'll have to wait.

People

Vote (20)
Watch (21)

Dates

  • Created:
    Updated:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.