Another issue i have getting the build running on a new machine is
that the Java CAA compliance test suite always fails with an
OutOfMemoryError. It doesn't matter how I run that, in a full build
the suite on its own, or what memory setting i use it always ends up
getting the following exception in
On Mon, May 9, 2011 at 11:47 AM, ant elder wrote:
> Another issue i have getting the build running on a new machine is
> that the Java CAA compliance test suite always fails with an
> OutOfMemoryError. It doesn't matter how I run that, in a full build
> the suite on its own, or what memory setting
On Mon, May 9, 2011 at 11:51 AM, Simon Laws wrote:
> On Mon, May 9, 2011 at 11:47 AM, ant elder wrote:
>> Another issue i have getting the build running on a new machine is
>> that the Java CAA compliance test suite always fails with an
>> OutOfMemoryError. It doesn't matter how I run that, in a
The maven option won't help as surefire plugin forks the jvm. Try to configure
the surefire plugin.
Raymond Feng
Sent from my iPhone
On May 9, 2011, at 4:41 AM, ant elder wrote:
> On Mon, May 9, 2011 at 11:51 AM, Simon Laws wrote:
>> On Mon, May 9, 2011 at 11:47 AM, ant elder wrote:
>>> Anot
Thats a good point, i shall go play around with surefire config in the
tuscany-compliance-test-java-caa to see if that helps.
...ant
On Mon, May 9, 2011 at 4:45 PM, Raymond Feng wrote:
> The maven option won't help as surefire plugin forks the jvm. Try to
> configure the surefire plugin.
>
>
It turns out that there was already a surefire plugin config on the
test module which was setting some memory settings, but if i removed
them it all started working fine. I've committed that change and
kicked off a Hudson build to see if that still works, but if these
settings break it for anyone e
