[
https://issues.apache.org/jira/browse/METRON-666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15826171#comment-15826171
]
ASF GitHub Bot commented on METRON-666:
---------------------------------------
Github user jjmeyer0 commented on the issue:
https://github.com/apache/incubator-metron/pull/418
If time outs are going to continue being an issue, maybe we should start
looking into using Maven's parallel builds. For example, when I build locally I
always do: `mvn -T 2C clean package`. This means build using 2 threads per
core. It usually cuts the build time in half for me.
> 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)
