JackPGreen opened a new issue, #1326:
URL: https://github.com/apache/maven-javadoc-plugin/issues/1326

   ### Affected version
   
   3.12.0
   
   ### Bug description
   
   The 
[documentation](https://maven.apache.org/plugins/maven-javadoc-plugin/aggregate-jar-mojo.html)
 says the `javadoc:aggregate-jar` goal isn't thread safe, leading to warnings 
when executed with a parallel build:
   > Warning:  *****************************************************************
   Warning:  * Your build is requesting parallel execution, but this         *
   Warning:  * project contains the following plugin(s) that have goals not  *
   Warning:  * marked as thread-safe to support parallel execution.          *
   Warning:  * While this /may/ work fine, please look for plugin updates    *
   Warning:  * and/or request plugins be made thread-safe.                   *
   Warning:  * If reporting an issue, report it against the plugin in        *
   Warning:  * question, not against Apache Maven.                           *
   Warning:  *****************************************************************
   Warning:  The following plugins are not marked as thread-safe in my-project:
   Warning:    org.apache.maven.plugins:maven-javadoc-plugin:3.12.0
   Warning:  
   Warning:  Enable debug to see precisely which goals are not marked as 
thread-safe.
   Warning:  *****************************************************************
   
   Other goals _are_ declared thread-safe:
   
https://github.com/apache/maven-javadoc-plugin/blob/a308a1444b97943fe827befbd0dc25510268fc55/src/main/java/org/apache/maven/plugins/javadoc/JavadocNoForkReport.java#L45
   
   So I suspect that rather than being _not_ thread-safe, this annotation is 
simply missing from the other goals?


-- 
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]

Reply via email to