Re: [Geotools-devel] Why does Hudson use -Dtest.maxHeapSize=256M

[Ben Caradoc-D. <Ben...@cs...>]

That would be great! We need to fix it for GeoServer too. In each case, 
Hudson should be consistent with the pom, to avoid unpleasant surprises. 
(Even building with -Dall was a nasty trap until I added this to our 
builds; too easy to have a local build pass and Hudson fail.)

Justin Deoliveira wrote:
> The reason this was put in there was to tame the build. Before this was 
> sit getting a build server able to handle the geotools build was a bit 
> challenging. So I fear if we remove it it will lead to a much less 
> stable build server. But I am willing to try it out though.
> 
> -Justin
> 
> Ben Caradoc-Davies wrote:
>> Ben Caradoc-Davies wrote:
>>> I can't figure out why app-schema fails to build on Hudson.
>> Justin, I think I found the problem:
>> http://hudson.opengeo.org/hudson/job/geotools-trunk/1792/consoleText
>>
>> [gt_trunk] $ /opt/actual/apache-maven-2.1.0/bin/mvn -U clean install 
>> -Djava.awt.headless=true -Dtest.maxHeapSize=256M -Dall
>>
>> Why does Hudson use -Dtest.maxHeapSize=256M when the main pom sets this 
>> to 512M?
>>
>> Can we get rid of this option?
>>
> 
> 


-- 
Ben Caradoc-Davies <Ben...@cs...>
Software Engineer, CSIRO Exploration and Mining
Australian Resources Research Centre
26 Dick Perry Ave, Kensington WA 6151, Australia