Re: Javadoc: single configuration
Hi Stanimir, Stanimir Stamenkov wrote: states it should behave as you expect. May be it is a bug in the javadoc plugin, but I can't say for sure. Do you use the latest (2.9) plugin version? Does it happen with Maven 2 or 3, or both? I'm using maven 3.0.4, java 1.6.0_27 (openjdk), and maven-javadoc-plugin 2.9. Would you like me to file a bug? I couldn't figure out how to create an account on the bug tracker... Ultimately I'm trying to define the javadoc configuration once and have it apply to all invocations of the javadoc plugin. You may try defining the common configuration in a build/pluginManagement section, but again I don't know if it's supposed to work that way (for the reporting configuration) I tried just defining the configuration in the build/pluginManagement sections, but then `mvn site` didn't use it. The workaround I've developed is to define the configuration in the build section and then add an execution for the site phase: execution idsite-javadoc/id phasesite/phase goals goaljavadoc/goal goaltest-javadoc/goal /goals /execution I just tried the workaround this moring and it seems to be working well. Regards, Evan - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Javadoc: single configuration
Mon, 3 Jun 2013 07:04:58 -0700 (PDT), /Evan/: http://maven.apache.org/plugins/maven-javadoc-plugin/usage.html#Javadoc_Configuration That section warns me that the behaviour is different, but not *how* it differs. In the example at the bottom of that page the javadoc:javadoc uses elements from the configuration defined in the build *and* reporting sections: |mvn javadoc:javadoc |It will generate the Javadoc for private members (defined in build/) |using the stylesheet (defined in reporting/), and with no help page |(defined in build/). This is the documented behaviour that I can not reproduce. ( mvn javadoc:javadoc only looks at the configuration in the build section instead of both build and reporting sections) I see your point now. The documentation, including at the linked: http://maven.apache.org/guides/mini/guide-configuring-plugins.html#Using_the_reporting_Tag_VS_build_Tag states it should behave as you expect. May be it is a bug in the javadoc plugin, but I can't say for sure. Do you use the latest (2.9) plugin version? Does it happen with Maven 2 or 3, or both? Ultimately I'm trying to define the javadoc configuration once and have it apply to all invocations of the javadoc plugin. You may try defining the common configuration in a build/pluginManagement section, but again I don't know if it's supposed to work that way (for the reporting configuration). -- Stanimir - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Javadoc: single configuration
Hm, I fail to find such reference, and I'm actually reading `mvn site` and `mvn javadoc:javadoc` behave differently, given they are configured in different sections (reporting vs. build): | IMPORTANT NOTE: configuring the Javadoc plugin in the | reporting/ or build/ elements in the pom have NOT the same | behavior as described in the Guide to Configuring Plug-ins. Stanimir That section warns me that the behaviour is different, but not *how* it differs. In the example at the bottom of that page the javadoc:javadoc uses elements from the configuration defined in the build *and* reporting sections: |mvn javadoc:javadoc |It will generate the Javadoc for private members (defined in build/) |using the stylesheet (defined in reporting/), and with no help page |(defined in build/). This is the documented behaviour that I can not reproduce. ( mvn javadoc:javadoc only looks at the configuration in the build section instead of both build and reporting sections) Ultimately I'm trying to define the javadoc configuration once and have it apply to all invocations of the javadoc plugin. Regards, Evan -- View this message in context: http://maven.40175.n5.nabble.com/Javadoc-single-configuration-tp5757784p5758128.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Javadoc: single configuration
Fri, 31 May 2013 17:14:31 -0400, /Evan Ward/: I'm trying to configure the javadoc report plugin so that I get the same output with `mvn javadoc:jar` and `mvn site`. I've read the usage page [1] which suggests that configuring the plugin in the reporting section will apply the same configuration to the javadoc:jar invocation. Hm, I fail to find such reference, and I'm actually reading `mvn site` and `mvn javadoc:javadoc` behave differently, given they are configured in different sections (reporting vs. build): | IMPORTANT NOTE: configuring the Javadoc plugin in the | reporting/ or build/ elements in the pom have NOT the same | behavior as described in the Guide to Configuring Plug-ins. [1] http://maven.apache.org/plugins/maven-javadoc-plugin/usage.html#Javadoc_Configuration -- Stanimir - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Javadoc: single configuration
Hi, Thanks for the great product! I'm trying to configure the javadoc report plugin so that I get the same output with `mvn javadoc:jar` and `mvn site`. I've read the usage page [1] which suggests that configuring the plugin in the reporting section will apply the same configuration to the javadoc:jar invocation. This has not been my experience. By running with '-Ddebug=true' and checking the options file I've seen that configuring the plugin in reporting only affects the site invocation. Similarly, configuring the plugin in the build section only affects the javadoc:jar invocation. Am I missing something or is this a bug? I can provide a sample project as a test case. I would really like to avoid copying a large section of my pom. :) Regards, Evan [1] http://maven.apache.org/plugins/maven-javadoc-plugin/usage.html#Javadoc_Configuration - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
