[
https://issues.apache.org/jira/browse/MJAVADOC-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17958077#comment-17958077
]
Olivier Lamy commented on MJAVADOC-694:
---------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-javadoc-plugin#1070|https://github.com/apache/maven-javadoc-plugin/issues/1070].
> Empty warning with maven-javadoc-plugin 3.3.1
> ---------------------------------------------
>
> Key: MJAVADOC-694
> URL: https://issues.apache.org/jira/browse/MJAVADOC-694
> Project: Maven Javadoc Plugin (Moved to GitHub Issues)
> Issue Type: Bug
> Affects Versions: 3.3.1
> Reporter: Simon
> Assignee: Slawomir Jaranowski
> Priority: Minor
> Fix For: 3.3.2
>
>
> I tested recently to upgrade to v3.3.1 and I get an empyt [WARNING] in my
> maven logs.
> Tested with v3.3.0, v3.2.0 and v3.1.1 and I don't face this issue.
> E.g. :
> {code:java}
> [INFO] <<< maven-javadoc-plugin:3.3.1:javadoc (default-cli) <
> generate-sources @ leshan-server-redis <<<
> [INFO]
> [INFO]
> [INFO] --- maven-javadoc-plugin:3.3.1:javadoc (default-cli) @
> leshan-server-redis ---
> [WARNING]
> [INFO] Configuration changed, re-generating javadoc.
> [INFO]
> [INFO] ---------------< org.eclipse.leshan:leshan-client-core
> >----------------
> [INFO] Building leshan - client core 2.0.0-SNAPSHOT
> [7/14]
> [INFO] -------------------------------[ bundle
> ]-------------------------------
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
