You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Joacim J <jo...@gmail.com> on 2010/07/02 09:16:51 UTC

Re: Strange surefire error

Update:
We are currently using
forkMode=never

and it works

Regards Joacim



On Fri, Jun 18, 2010 at 7:20 AM, Joacim J <jo...@gmail.com> wrote:

>
>
> On Tue, Jun 15, 2010 at 8:02 AM, Kristian Rosenvold <
> kristian.rosenvold@gmail.com> wrote:
>
>> Does it fail "immediately" or does it run the tests first ?
>>
>> Is the plugin configured with forkedProcessTimeoutInSeconds ?
>>
>> Kristian
>>
>>
>
> Yes, it fails directly.
> I have configured to use plexus-utils v.1.5.9 and surefire plugin 2.5 now,
> still not working.
> Tested with different JVMs to build the plexus-util
>
> Sun's JVM 1.5.0 => OK
> Sun's JVM 1.6.0 => OK
> IBM's JVM 1.5.0 => NOK (3 tests failed)
> IBM's JVM 1.6.0 => NOK (33 tests failed)
>
>
> With IBM's JVM 1.5.0 it still works for us so our "problem" with IBM's JVM
> 1.6.0 should be in the new 33 failed test.
>
> The approach we have right now is to define Sun's JVM on surefire-plugin
> and to use:
> forkMode=always
> forkedProcessTimeoutInSeconds=60
>
> The team have executed once and succeeded so will do som more tests. Still
> it's a workaround and it would be best if plexus-util would work with IBM
> JVM :)
>
>
> --
> Regards
> Joacim
>



-- 
Regards
Joacim