Thanks, it was the MaxPermSize that I needed to set. And I set them all to
512m and it still worked.
Brian
On 2/10/06, Daniel Beland <[EMAIL PROTECTED]> wrote:
>
> This is what I had to set to prevent all errors when building the site
> with
> a lot of reports
>
> MAVEN_OPTS=" -Xmx1024m -Xms1024m
This is what I had to set to prevent all errors when building the site with
a lot of reports
MAVEN_OPTS=" -Xmx1024m -Xms1024m -XX:MaxPermSize=512m"
I don't think the values need to be that high, but I think it is important
to increase the MaxPermSize which is 32M by default I think
On 2/10/06,
I had the same problem. However, increasing the memory via MAVEN_OPTS
didn't help at all. Then I tried setting the findbugs plugin variable
maven.findbugs.jvmargs=-Xmx512m but that didn't help either.
In the end I upgraded from plugin version 1.0 to version 1.1 and the out
of memory error disappear
I've tried 512, and that's all the memory I have on this laptop. Would it
really require more than that for one report? I only have the findbugs
report running in my pom right now.
Brian
On 2/10/06, Jeff Jensen <[EMAIL PROTECTED]> wrote:
>
> Perhaps set that value higher?
>
>
> Quoting Brian Burr
Perhaps set that value higher?
Quoting Brian Burridge <[EMAIL PROTECTED]>:
> When I run the findbugs plugin I a getting an out of memory error: java heap
> sapce.
>
> I have set MAVEN_OPTS="-Xmx400m"
>
> Is there something else I should set as well?
>
> Brian
>
--
When I run the findbugs plugin I a getting an out of memory error: java heap
sapce.
I have set MAVEN_OPTS="-Xmx400m"
Is there something else I should set as well?
Brian
