I have a Maven parent POM that contains org.apache.maven.plugins:maven-javadoc-plugin:2.8 under <pluginManagement/>. Under build/plugins/plugin, I have org.apache.maven.plugins:maven-site-plugin:3.0 , with a configuration/reportPlugins/plugin for org.apache.maven.plugins:maven-javadoc-plugin - along with several other reporting plugins.
This works great for most of my child projects. However, I have at least one project where I need to add a link to http://download.oracle.com/javaee/5/api/ (using configuration/links/link). This works great for building the Javadoc jar (javadoc:jar), but the links are not being added for the Javadocs being generated for the site. There are a number of related issues going on here, so I apologize that I'm not exactly sure where to start. As I mentioned, the "javadoc:jar" is working exactly as expected. Additionally, when generating the site, it shows: [INFO] Skipped "JavaDocs" report, file "apidocs/index.html" already exists for the English version. However, a few lines later, it continues to re-generate the JavaDocs anyway: [INFO] Generating "JavaDocs" report --- maven-javadoc-plugin:2.8 When it does this, it does not use the additional links that were configured in the plugin. Now granted, the Java EE Javadocs are probably common enough that I could probably just add the link to the parent - but what if this was a unique Javadoc dependency that only impacted a given child project, or if I didn't have access to update the parent? I tried moving my link configuration from build/plugins/plugin to build/pluginManagement/plugins/plugin . This still worked for the javadoc:jar, but not for the reporting goal. I then tried to extend the reporting configuration in my child project. I added a build/plugin for org.apache.maven.plugins:maven-site-plugin:3.0, just as in the parent, and added a configuration/reportPlugins/plugin for the javadoc plugin, with a repeated configuration for the links to be used. This worked great, as the links were then made within the site Javadocs - but then all other site plugins were no longer being executed. It seems by re-defining <reportPlugins/>, the plugin list was overwritten instead of appended to? I'm using the latest Maven versions of everything. Please let me know if this is a known issue (possibly related to the reporting / site overhaul that appears to have happened for Maven 3), if additional details or examples are needed, or if this should be a candidate for a bug report. Thanks!! -- Mark A. Ziesemer -- View this message in context: http://maven.40175.n5.nabble.com/Relation-between-reporting-plugins-and-build-plugins-pluginManagment-in-Maven-3-tp4670353p4670353.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
