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)
Signup
Maven 2.x and 3.x Site Plugin
  • Maven 2.x and 3.x Site Plugin
  • MSITE-443

add a reportingManagement section

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 3.0
  • Component/s: None
  • Labels:
    None
  • Environment:
    maven-site-plugin 2.0-beta-3-SNAPSHOT
  • Number of attachments :
    0

Description

Consider the following POM:

<!-- ... ... -->
<!-- ... ... -->
<build>
    <pluginManagement>
        <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-javadoc-plugin</artifactId>
            <configuration>
            <author>false</author>
            </configuration>
        </plugin>
    </pluginManagement>
</build>
<!-- ... ... -->
<!-- ... ... -->
<reporting>
    <plugins>
        <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-javadoc-plugin</artifactId>
        </plugin>
    </plugins>
</reporting>
<!-- ... ... -->

mvn site:site doesn't honor the javadoc configuration specified in the <pluginManagement/> section.
However, mvn javadoc:javadoc honors them.

This is true not just for javadoc but other plugins like checkstyle as well.

I guess, the <reporting/> section doesn't use the <pluginManagement/> section at all.

Issue Links

is duplicated by

Bug - A problem which impairs or prevents the functions of the product. MNG-3385 PluginManagement does not work for report-plugins

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

Improvement - An improvement or enhancement to an existing feature or task. MSITE-444 reporting section should allow additional dependencies in plugins as well

  • 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. MSITE-516 reportPlugins should/could inherit more information from pluginManagement

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

Improvement - An improvement or enhancement to an existing feature or task. MSITE-523 Configuring build and reporting goals (under reportPlugins) requires duplication

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

Activity

  • All
  • Comments
  • Work Log
  • History
  • Activity

People

  • Assignee:
    Unassigned
    Reporter:
    Indrajit Raychaudhuri
Vote (86)
Watch (82)

Dates

  • Created:
    16/Dec/05 8:58 AM
    Updated:
    18/Sep/12 8:41 AM
    Resolved:
    16/Sep/12 10:04 AM
  • Atlassian JIRA (v5.2.7#850-sha1:b2af0c8)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.