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 & 3
  • MNG-3385

PluginManagement does not work for report-plugins

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Duplicate
  • Affects Version/s: 2.0.8
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None

Description

<build>
...
</pluginManagement>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-pmd-plugin</artifactId>
<version>2.2</version>
</plugin>
</plugins>
</pluginManagement>
...
</build>
<reporting>
<plugins>
<plugin>
<artifactId>maven-pmd-plugin</artifactId>
</plugin>
</plugins>
</reporting>

mvn site ... use pmd-2.4-SNAPSHOT instead of the defined 2.2 ... why?

Issue Links

duplicates

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.

Improvement - An improvement or enhancement to an existing feature or task. MNG-2578 Make it possible to set default versions for reporting-plugins (i.e. plugins under <reporting>)

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

Bug - A problem which impairs or prevents the functions of the product. MJAVADOC-167 Mixing Standard/Custom Tags for Ordering Failure

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • 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-3521 mvn site does not use the plugin version from the pluginManagement section

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

Bug - A problem which impairs or prevents the functions of the product. MNG-4419 Plugin versions of a reporting section are not inherited from the pluginManagement section of a parent pom and default to nearest *-SNAPSHOT

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

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
Vincent Siveton added a comment - 06/Feb/08 6:00 AM

I guess <reporting><reportingManagement/></reporting> should be better

Show
Vincent Siveton added a comment - 06/Feb/08 6:00 AM I guess <reporting><reportingManagement/></reporting> should be better
Hide
Permalink
Paul Benedict added a comment - 24/Mar/08 4:38 PM

Wny not just <pluginManagement> inside of <reporting>?

Show
Paul Benedict added a comment - 24/Mar/08 4:38 PM Wny not just <pluginManagement> inside of <reporting>?
Hide
Permalink
Benjamin Bentmann added a comment - 24/Mar/08 4:53 PM

Wny not just <pluginManagement> inside of <reporting>?

+1, sounds reasonable with regard to consistency compared to existing POM structure. Right now, there is no <build>.<buildManagement> section, it's called <pluginManagement> because it contains plugins, the same would go for <reporting>.

Show
Benjamin Bentmann added a comment - 24/Mar/08 4:53 PM
Wny not just <pluginManagement> inside of <reporting>?
+1, sounds reasonable with regard to consistency compared to existing POM structure. Right now, there is no <build>.<buildManagement> section, it's called <pluginManagement> because it contains plugins, the same would go for <reporting>.
Hide
Permalink
Paul Benedict added a comment - 24/Mar/08 10:38 PM

I fell into this trap myself. Last week, I defined my reporting plugin versions in my build's <pluginManagement> section, just to find out it has no effect on the site generation. This to me is definitively a high-priority issue since I cannot dictate the report versions to use without actually specifying the reports themselves.

Show
Paul Benedict added a comment - 24/Mar/08 10:38 PM I fell into this trap myself. Last week, I defined my reporting plugin versions in my build's <pluginManagement> section, just to find out it has no effect on the site generation. This to me is definitively a high-priority issue since I cannot dictate the report versions to use without actually specifying the reports themselves.
Hide
Permalink
Carlos Sanchez added a comment - 28/Oct/08 8:53 PM

See linked issues

Show
Carlos Sanchez added a comment - 28/Oct/08 8:53 PM See linked issues

People

  • Assignee:
    Carlos Sanchez
    Reporter:
    Andreas Höhmann
Vote (4)
Watch (8)

Dates

  • Created:
    06/Feb/08 2:56 AM
    Updated:
    30/Oct/09 10:14 AM
    Resolved:
    28/Oct/08 8:53 PM
  • 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.