Description of problem:
When batik is being built and javadoc tool runs out of memory (or encounters some other failure) batik will still succesfully finish build but will produce incomplete javadocs.
javadoc task should have failonerror="yes" added so that whole build fails in these cases.
As for OOM problem a change of maxmemory="128m" to higher limit (512m for example) solves the issue.
Version-Release number of selected component (if applicable):
most of the time during builds. Look for "java.lang.OutOfMemoryError" in build logs
Steps to Reproduce:
1. build the package (rpmbuild)
Incomplete javadoc, errors in build logs
failed build in case of problems, otherwise complete javadoc
When adding line
sed -i 's/maxmemory=.*/maxmemory="50m"/' build.xml
to the beginning of %build section, rhpkg local fails.
Yes, when I done with the previous commit in the packaging repo (commit 83e2f9e16a3b24d01033fab6dbe87da5d7301f16) then build didn’t fail and batik-javadoc subpackage is empty.
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.