[
https://issues.apache.org/jira/browse/MESOS-3126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14642093#comment-14642093
]
Hans van den Bogert commented on MESOS-3126:
--------------------------------------------
No, the oom error is a red herring. It stems from the rather significant errors
amount caused by the javadoc plugin. Ive increased the heapspace and the only
difference is that it then actually outputs the errors in detail.
> Building mesos.jar, uses old javadoc plugin in maven.
> -----------------------------------------------------
>
> Key: MESOS-3126
> URL: https://issues.apache.org/jira/browse/MESOS-3126
> Project: Mesos
> Issue Type: Bug
> Components: build
> Affects Versions: 0.23.0
> Environment: Centos 6.5.
> Manually installed maven, version 3.3.3
> Manually installing mesos.
> Reporter: Hans van den Bogert
> Priority: Minor
>
> When building Mesos, including the mesos.jar. It errors when generating the
> javadoc:
> http://pastebin.com/TNRERS4p
> It seems the javadoc plugin is also trying to parse .class files, though the
> source directories are correct in the pom file.
> Further investigation leads to think that the javadoc plugin version is to
> blame. Setting a fixed version of 2.10.3 for the javadoc plugin, in the pom
> file, successfully generates the javadoc.
> In this environment, the default javadoc plugin being downloaded, is 2.8.1
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
