[
https://issues.apache.org/jira/browse/MJAVADOC-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MJAVADOC-401.
-----------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period
of time. If you think this issue still applies, retest your problem with the
most recent version of Maven and the affected component, reopen and post your
results.
> maven-javadoc-plugin should have option to fail on JavaDoc warning
> ------------------------------------------------------------------
>
> Key: MJAVADOC-401
> URL: https://issues.apache.org/jira/browse/MJAVADOC-401
> Project: Maven Javadoc Plugin
> Issue Type: Improvement
> Reporter: Michael Vorburger
> Priority: Major
>
> git clone https://github.com/vorburger/MariaDB4j.git; cd MariaDB4j
> git checkout ab3a08fa557a26c384c9fa3408c57751c77fea76
> mvn -Dmaven.test.skip=true -Prelease package
> {noformat}[INFO] --- maven-javadoc-plugin:2.9.1:jar (attach-javadocs) @
> mariaDB4j ---
> [INFO]
> 4 warnings
> [WARNING] Javadoc Warnings
> [WARNING]
> /home/vorburger/dev/M/MariaDB4j/src/main/java/ch/vorburger/exec/ManagedProcess.java:295:
> warning - @value tag (which references INVALID_EXITVALUE) can only be used
> in constants.
> [WARNING]
> /home/vorburger/dev/M/MariaDB4j/src/main/java/ch/vorburger/exec/ManagedProcess.java:305:
> warning - @value tag (which references INVALID_EXITVALUE) can only be used
> in constants.
> [WARNING]
> /home/vorburger/dev/M/MariaDB4j/src/main/java/ch/vorburger/exec/ManagedProcessBuilder.java:119:
> warning - Tag @see: can't find environment(File) in java.lang.ProcessBuilder
> [WARNING]
> /home/vorburger/dev/M/MariaDB4j/src/main/java/ch/vorburger/exec/UnknownPlatformException.java:29:
> warning - Tag @see: reference not found: Platform#is()
> [INFO] Building jar:
> /home/vorburger/dev/M/MariaDB4j/target/mariaDB4j-2.0.0-SNAPSHOT-javadoc.jar{noformat}
> I'd like a new failOnWarning kind of option for it fail in case of such
> WARNINGs from JavaDoc. (My understanding is that the currently available
> failOnError which is already true doesn't catch this.)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
