jira-importer commented on issue #696: URL: https://github.com/apache/maven-javadoc-plugin/issues/696#issuecomment-2957346657
**[Sebb](https://issues.apache.org/jira/secure/[email protected])** commented That's another possibility, but I still think the Javadoc plugin needs to be told the class name to load. It seems wrong to fix the class name within the Javadoc plugin, so at least it should be possible to override the default. Ideally via a user property as well, so the user can add it to their settings.xml Unfortunately the Oracle tool has some bugs, so it would be useful to be able to use a 3rd party version of the tool which does not have those bugs. That is likely to have a different name. The user can still add the jar to lib/ext if they wish, or add it to the classpath via a dependency. Using lib/ext means no change to poms, but the jar will likel be lost if the Maven installation is updated. Using a dependency works with any Maven installation. -- 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]
