Java 8 is a bit more strict in JavaDoc parsing. This can lead to build failures in Maven when building the repo with warnings like:
Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:2.7:jar (attach-javadocs) on project [projectname]: MavenReportException: Error while creating archive:
Exit code: 1 - [path-to-file]:[linenumber]: warning: no description for @param
Sure, the good solution would be to fix the JavaDocs. But in cases where you just clone a foreign repo, you probably just want to get it run and not start fixing it.
To ignore the erros, just turn off doclint by adding the following <configuration>
tag to your pom.xml
:
<plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-javadoc-plugin</artifactId> <version>2.10.2</version> <executions> <execution> <id>attach-javadocs</id> <goals> <goal>jar</goal> </goals> <configuration> <!-- add this to disable checking --> <additionalparam>-Xdoclint:none</additionalparam> </configuration> </execution> </executions> </plugin>
Some more solutions can be found in this StackOverflow thread.
nope, this seems to be ignored by maven. No any difference. javadoc plugin still complaining about perfectly fine javadoc generated by eclipse…
looks like apache now decided to have their own rules how code comments should look like
This works for me. Make sure maven-javadoc-plugin version matches yours.