jira-importer commented on issue #844: URL: https://github.com/apache/maven-javadoc-plugin/issues/844#issuecomment-2957357151
**[Alexander Kriegisch](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=kriegaex)** commented Thanks to all of you who commented before me, trying to get to to the bottom of this. It was quite instructive to read those comments. Wow, that is really subtle and was not understandable for me when reading the docs: * `javadoc:javadoc` puts the javadocs into `target/site/apidocs` by default, but * `javadoc:jar` puts them into `target/apidocs`. I really thought, that they would always end up in `target/apidocs` when using the mojo stand-alone and in `target/site/apidocs` when creating a Maven site only. I even modeled my own plugin after this assumption, reading the Maven Javadoc documentation as a template. Actually, I am disappointed that the real behaviour is different. I think, it would have made sense if a stand-alone mojo report has another structure and output directory than a collection of reports like a Maven site. But of course, that is arguable. When changing any behaviour and documentation for plugin version 4 and Doxia 2, please do not forget that for many years, users will still continue to use the current version in their existing projects, shying away from upgrading many dependencies, which, as I have experienced, can be a quite non-trivial challenge in case of Doxia 2. Therefore, I plead for more precise documentation in the currently maintained version, too. -- 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]
