maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sven Ludwig (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MSITE-443) add a reportingManagement section
Date Thu, 04 Feb 2010 00:22:55 GMT

    [ http://jira.codehaus.org/browse/MSITE-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209104#action_209104
] 

Sven Ludwig commented on MSITE-443:
-----------------------------------

I want to add an idea how to solve this issue. It could be done by offering a new boolean
property in the reporting section like "honorPluginManagement". Default should be false, but
if it is set to true, the plugins in the reporting section would use the respective configurations
in pluginManagement. It should then also be possible to override pluginManagement settings
in the reporting section. Moreover, it should work no matter if the reporting section is in
the same pom as the pluginManagement section, or if it is further down the inheritance tree.
At least from my current personal perspective, this would be a good solution. ;-)

I can see however that some people may want a separate pluginManagement-like section within
the reporting section.

> add a reportingManagement section
> ---------------------------------
>
>                 Key: MSITE-443
>                 URL: http://jira.codehaus.org/browse/MSITE-443
>             Project: Maven 2.x Site Plugin
>          Issue Type: Bug
>         Environment: maven-site-plugin 2.0-beta-3-SNAPSHOT
>            Reporter: Indrajit Raychaudhuri
>             Fix For: 3.0-alpha-1
>
>
> Consider the following POM:
> {code:xml}
> <!-- ... ... -->
> <!-- ... ... -->
> <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>
> <!-- ... ... -->
> {code}
> {{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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message