jira-importer commented on issue #697: URL: https://github.com/apache/maven-javadoc-plugin/issues/697#issuecomment-2957346797
**[Damon Smith](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=damonsmith)** commented It's all very well to say "remember to specify every version of every plugin" but I was not even aware that my release build was using the javadoc plugin! About a year ago I painstakingly set up a full build with config for release, signed artifacts, nexus repositories, deployment, everything was working well, and then I come back, make some code changes and run a release and the javadoc plugin (that I didn't even realise I was running and have no interest in) is now breaking my entire build and requiring lots of investigation, changes to my versions and pluginManagement config, all of the skip config from the command line fails (I assume it's because it's a release build so the skip isn't passed through). And there's no good documentation on how to even run the generate javadoc step, let alone how to prevent it from running. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
