[
https://issues.apache.org/jira/browse/METRON-666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15825641#comment-15825641
]
ASF GitHub Bot commented on METRON-666:
---------------------------------------
GitHub user mattf-horton opened a pull request:
https://github.com/apache/incubator-metron/pull/418
METRON-666 Fix javadoc doclint errors
Fixes for Java 8 javadocs automatic doclint problems:
- replaced many uses of `<p/>` and `</p>` with simple uses of `<p>`
- wrapped uses of `<` or `>` in `{@literal}` or equivalent
- a couple actual errors like \@return with no description or \@throws when
nothing thrown
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mattf-horton/incubator-metron METRON-666
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-metron/pull/418.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #418
----
commit a8a192ebff6598d08400320731b28a913ab0c417
Author: mattf-horton <[email protected]>
Date: 2017-01-17T08:22:08Z
METRON-666 Fix javadoc doclint errors
----
> Fix javadoc doclint errors
> --------------------------
>
> Key: METRON-666
> URL: https://issues.apache.org/jira/browse/METRON-666
> Project: Metron
> Issue Type: Bug
> Affects Versions: 0.3.0
> Reporter: Matt Foley
> Assignee: Matt Foley
>
> Java 8 includes "doclint" as part of javadocs. As a result, running javadoc
> on current code base has fatal errors, mostly (not all) related to use of
> "<p/>" (not allowed ever), or unmatched "</p>" (not preceded by a matching
> "<p>"). It is, however, happy with unmatched "<p>", so that's the thing to
> use for paragraph separators. Put it on the same line as the next line of
> text to avoid a warning about "empty <p>".
> There are other errors fixed here too.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
