jira-importer commented on issue #884: URL: https://github.com/apache/maven-javadoc-plugin/issues/884#issuecomment-2957359348
**[Jeremy Landis](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=hazendaz)** commented [Robert Scholte](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rfscholte) This still feels like a bug here. The parameter is provided by maven javadoc plugin in https://github.com/apache/maven-javadoc-plugin/blob/master/src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java line #5316. The issue presents itself when automatic module naming is used throughout and classpath is still present. Per the error, its not unnamed, its named per automatic module naming. Could a fix be added to not add that flag when automtic module naming is in use? ``` | | |if ( mainResolvePathResult != null| |&& ModuleNameSource.MANIFEST.equals( mainResolvePathResult.getModuleNameSource() ) )| |{| |arguments.add( "--add-modules" );| |arguments.add( "ALL-MODULE-PATH" );| } ``` Or at very least some way to turn this off? My use case is that I need to run javadoc plugin during verify stages spefically to enforce clean javadocs during builds before we get to CI. Only fixes I've seen talk about turning that off during such cycles which defeats the purpose. Due to this issue, when targetting jdk 11, I have to force \<source> and \<release> on the javadoc plugin back to 8 in order to work. That in turn throws warnings like crazy when java 11 constructs used like 'var'. Perference would be that this actually works and best I can tell, adding of that flag isn't allowed. We are using jdk 11.0.12 from oracle currently. Unless something else is going on causing this that is being done wrong, the easiest solution seems to be to add a flag to not add that if not wanted (at least without putting any thought into it). -- 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]
