[
https://issues.apache.org/jira/browse/BIGTOP-1303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13994364#comment-13994364
]
Konstantin Boudnik commented on BIGTOP-1303:
--------------------------------------------
Thanks for looking into this Giri! Unfortunately - I still see the issue, even
I bump the forrest.memory to 512m. This is the list of broken links from the
build:
{noformat}
cat build/pig/rpm/BUILD/pig-0.12.1/src/docs/build/site/broken-links.xml
<broken-links>
<link message="No pipeline matched request: linkmap.pdf">linkmap.pdf</link>
<link message="No pipeline matched request: cont.pdf">cont.pdf</link>
<link message="No pipeline matched request:
pig-index.pdf">pig-index.pdf</link>
<link message="No pipeline matched request: start.pdf">start.pdf</link>
<link message="No pipeline matched request: basic.pdf">basic.pdf</link>
<link message="No pipeline matched request: udf.pdf">udf.pdf</link>
<link message="No pipeline matched request: index.pdf">index.pdf</link>
<link message="No pipeline matched request: admin.pdf">admin.pdf</link>
<link message="No pipeline matched request: perf.pdf">perf.pdf</link>
<link message="No pipeline matched request: cmds.pdf">cmds.pdf</link>
<link message="No pipeline matched request: func.pdf">func.pdf</link>
<link message="No pipeline matched request: test.pdf">test.pdf</link>
</broken-links>
{noformat}
The weird part that I don't see any other error messages nor exceptions
anywhere in the build.
> Pig 0.12.1 build is broken at the site target. Stack build can't proceed
> ------------------------------------------------------------------------
>
> Key: BIGTOP-1303
> URL: https://issues.apache.org/jira/browse/BIGTOP-1303
> Project: Bigtop
> Issue Type: Bug
> Components: Debian, RPM
> Affects Versions: 0.7.0
> Reporter: Konstantin Boudnik
> Assignee: Giridharan Kesavan
> Priority: Blocker
> Fix For: 0.8.0
>
> Attachments:
> 0001-BIGTOP-1303-fix-Pig-0.12.1-build-is-broken-at-the-si.patch
>
>
> The site build doesn't go through. See the comment for the detailed message.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
