xmlgraphics-batik-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stanislav Ochotnicky (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (BATIK-1065) [patch] javadoc task should fail when OOM
Date Thu, 16 Jan 2014 13:27:21 GMT

     [ https://issues.apache.org/jira/browse/BATIK-1065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Stanislav Ochotnicky updated BATIK-1065:
----------------------------------------

    Attachment: batik-javadoc-task-failonerror-and-oom.patch

Proposed patch implementing the change

> [patch] javadoc task should fail when OOM
> -----------------------------------------
>
>                 Key: BATIK-1065
>                 URL: https://issues.apache.org/jira/browse/BATIK-1065
>             Project: Batik
>          Issue Type: Bug
>          Components: javadoc
>    Affects Versions: 1.8
>            Reporter: Stanislav Ochotnicky
>              Labels: OOM, build-failure, javadoc
>         Attachments: batik-javadoc-task-failonerror-and-oom.patch
>
>
> javadoc ant task doesn't define "failonerror" configuration to yes and therefore can
produce incomplete javadocs when error is encountered during build (such as OOM).
> Besides this maxmemory is currently set to 128MB which at least on my system causes very
long javadoc build times. After upping the maxmemory to 512MB the build process sped up significantly.
> Attached is a patch against trunk to add failonerror and raise maxmemory to 512MB for
javadoc task



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

---------------------------------------------------------------------
To unsubscribe, e-mail: batik-dev-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: batik-dev-help@xmlgraphics.apache.org


Mime
View raw message