jira-importer commented on issue #852: URL: https://github.com/apache/maven-javadoc-plugin/issues/852#issuecomment-2957357592
**[Gili](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=cowwoc)** commented If you are unable to come up with an easy fix for this issue, consider what [Jonathan wrote](https://bugs.openjdk.java.net/browse/JDK-8212233?focusedCommentId=14235193&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-14235193) a while back: > With respect to this issue, my going-in assumption is that if the module path, class path, automatic modules, etc have been set up for **javadoc in a way that mirrors the equivalent configuration for javac**, then it must be possible to set up links for API for the modules (and unnamed module) in a reasonably obvious manner. > > That may not be as detailed as you want to see at this point, but I hope it does outline the constraints for the design for a resolution. In theory, we should be able to argue that the Javadoc tool should accept module1 on the module-path, module2 on the classpath and things should just work. After all, they work this way for javac. It might be worth a try. -- 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]
