jira-importer commented on issue #411: URL: https://github.com/apache/maven-javadoc-plugin/issues/411#issuecomment-2957325251
**[Martin Desruisseaux](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=desruisseaux)** commented The way javadoc plugin currently work (passes the source file names) cause some trouble to us, because it prevent `@see` and `@link` tags to work with packages. For example if org.mypackage is a package, then `@see` org.mypackage is supposed to create a link to the package overview. This work well if the javadoc tool is used with the -subpackages parameters, but doesn't work when we pass the source file names. See MNG-1166 I would prefer if the javadoc plugin was using the -subpackages parameters instead of passing the source file names. It would fix both the -excludes issue and the `@see` org.mypackage issue. Or at least, the javadoc plugin should not pass the source filenames when the -subpackages parameter is used. Maybe the two approachs should be mutually exclusive. -- 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]
