[hibernate-dev] Problems building Core

[Hardy Ferentschik]

Hi,

turns out that MAVEN_OPTS does not help in this case at all. The surefire
plugin per default uses the forkMode 'once', meaning a new JVM gets created
for running the tests. Command line arguments passed via MAVEN_OPTS only  
apply
for the JVM running the build.

To increase the heap size for surefire you have to pass the JVM options in
the plugin configuration. See  
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4728

I added -Xmx1024 globally in the parent pom of Core. I think that's better  
than
just adding it to Envers alone.

I have no idea why no-one else has experienced this issue. Might be some  
JVM specific
thing.

--Hardy



On Mon, 21 Dec 2009 13:28:46 -0300, Adam Warski <adam at warski.org> wrote:

>
>> -Xmx1024 - that's what I used to have, mainly driven by the fact that  
>> once upon
>> a time the docbook plugin needed to work.
>>
>> Btw, I also have the problem if I just try to run the Envers build.
> That's very weird. I just ran all tests, a "clean install" took 1m 30s,  
> even with default maven memory settings (so no -Xmx in MAVE_OPTS).
> I'm using Maven 2.2.0 on Java 1.5.0_19 (32 bit - maybe that's the  
> problem?)
>
>> Have you only recently added more tests? I used to be able to build  
>> everything just fine.
>> Maybe the test suite can be split up? (eg by configuring two instances  
>> of the surefire plugin !?)
>> In case it the the report generator, maybe there is a way to configure  
>> another generator?
> Well I add some tests from time to time (basically when I fix a bug ;)  
> ), but nothing dramatical.
> I'm not too good with maven so I don't really know if it's possible to  
> do a split.
>
> Adam