Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
-
maven-site-plugin 2.0-beta-3-SNAPSHOT
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.
Attachments
Issue Links
- is duplicated by
-
MNG-3385 PluginManagement does not work for report-plugins
- Closed
- is related to
-
MPIR-300 Reporting plugins are reported with wrong version if version specified via pluginManagement
- Closed
-
MNG-5477 "malformed POM" warning issued when no version in reporting section
- Closed
-
MSITE-516 reportPlugins should/could inherit more information from pluginManagement
- Closed
-
MSITE-444 reporting section should allow additional dependencies in plugins as well
- Closed
- relates to
-
MNG-2578 Make it possible to set default versions for reporting-plugins (i.e. plugins under <reporting>)
- Closed
-
MSITE-523 Configuring build and reporting goals (under reportPlugins) requires duplication
- Closed
- supercedes
-
MSITE-444 reporting section should allow additional dependencies in plugins as well
- Closed