jira.codehaus.org

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What?s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • Maven 2.x and 3.x Site Plugin
  • MSITE-444

reporting section should allow additional dependencies in plugins as well

  • Log In
  • Views
    • XML
    • Word
    • Printable

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

Description

currently, you can only do this in the build section

Issue Links

is depended upon by

New Feature - A new feature of the product, which has yet to be developed. MPMD-22 PMD plugin <configuration> should accept dependency entries

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
is duplicated by

Bug - A problem which impairs or prevents the functions of the product. MNG-2173 support <dependencies> in <reporting> plugins

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
relates to

Bug - A problem which impairs or prevents the functions of the product. MSITE-443 add a reportingManagement section

  • Major - Major loss of function.
  • Open - The issue is open and ready for the assignee to start work on it.

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
md added a comment - 21/Nov/07 3: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

Show
md added a comment - 21/Nov/07 3: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
Hide
Permalink
Rémy Sanlaville added a comment - 16/Jul/08 6:16 AM

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 - 16/Jul/08 6:16 AM 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 - 22/Apr/09 4:18 PM - 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 - 22/Apr/09 4:18 PM - 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 - 23/Apr/09 9:44 AM

nm, guess this'll have to wait.

Show
John Casey added a comment - 23/Apr/09 9:44 AM nm, guess this'll have to wait.

People

  • Assignee:
    John Casey
    Reporter:
    Brett Porter
Vote (20)
Watch (22)

Dates

  • Created:
    09/Jan/06 3:49 PM
    Updated:
    16/May/10 11:58 AM
  • Atlassian JIRA (v5.0.4#731-sha1:3aa7374)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.