Lombok is actually capable of filling out a partially defined builder class, so you can declare enough of the builder to make Javadoc happy and leave it at that. No need to delombok. The following worked for me in this situation: @Data @Builder public class Foo { private String param; // Add this line and … Read more
Running maven with -T1C will cause maven to try to build modules in parallel, so if you have a multi-module project, at best it will build each module’s javadoc in parallel (if your dependency graph between modules allow it). The javadoc process itself is single-threaded, so you won’t be able to use multiple cores to … Read more
Using the same plugin, you can generate javadoc in a folder using mvn javadoc:javadoc It puts the help content under target/site/apidocs You can change the output folder by using the plugin configuration parameter reportOutputDirectory Please refer to: Apache Maven Javadoc Plugin
As suggested in OpenJDK issue tracker this can be worked around with defining source on Javadoc plugin: <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-javadoc-plugin</artifactId> <configuration> <source>8</source> </configuration> </plugin>
This appears to be due to javax.transaction.Transactional (or any other class in your classpath for that matter) being itself annotated with javax.interceptor.InterceptorBinding, which is missing in classpath unless explicitly declared in dependencies: @Inherited @InterceptorBinding // <– this ONE is causing troubles @Target({ElementType.TYPE, ElementType.METHOD}) @Retention(value = RetentionPolicy.RUNTIME) public @interface Transactional { Said that: javax.transaction.Transactional – comes … Read more
The Javadoc generation can be skipped by setting the property maven.javadoc.skip to true [1], i.e. -Dmaven.javadoc.skip=true (and not false)