Re: [I] [MJAVADOC-593] Module not found [maven-javadoc-plugin]
jira-importer commented on issue #885: URL: https://github.com/apache/maven-javadoc-plugin/issues/885#issuecomment-2957359401 **[Robert Scholte](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rfscholte)** commented Looks like a duplicate of MJAVADOC-576 -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] [MJAVADOC-593] Module not found [maven-javadoc-plugin]
jira-importer commented on issue #885: URL: https://github.com/apache/maven-javadoc-plugin/issues/885#issuecomment-2957359399 **[Robert Scholte](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rfscholte)** commented [Nibsi](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=Nibsi) The empty directory is created to be able to patch modules, so this is intended behavior. [Warkdev](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=Warkdev) Your project contains named and automatic modules, which means some patching needs to be done. In your case with `mvn compile javadoc:javadoc` it'll work. -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] [MJAVADOC-593] Module not found [maven-javadoc-plugin]
jira-importer commented on issue #885: URL: https://github.com/apache/maven-javadoc-plugin/issues/885#issuecomment-2957359395 **[Stephan van Hulst](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=nibsi)** commented Same problem here. It appears that the javadoc plugin generates a folder '`target/site/apidocs/src`' and then sets that folder as the `--module-source-path` in the `@options` file. It creates a folder inside for the module that it's generating documentation for, but the folder is empty. I think the plugin should be copying source files to the generated module folder. Additionally, instead of adding exported packages from the `module-info.java` to the packages command line argument of javadoc, it should probably just supply the module name with the `--module` command line switch. -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
