I've tried to deal with JVM crashes in the FailSafe (I was not having the
problem in SureFire) plugin by using:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-failsafe-plugin</artifactId>
<version>${hmp.failsafe.version}</version>
<configuration>
<forkCount>1</forkCount>
<reuseForks>false</reuseForks>
</configuration>
</plugin>
and then defining the plugin version in a property "hmp.failsafe.version"
which I can vary on the command line until I find one that works.
Gary
On Tue, Jul 7, 2020 at 6:38 AM Mukul Gandhi <gandhi.mu...@gmail.com> wrote:
> Hi Gary,
>
> On Sun, Jul 5, 2020 at 6:52 PM Gary Gregory <garydgreg...@gmail.com>
> wrote:
>
> You could try to set the fork count to 1.
> >
>
> As per Maven documentation, 'The default setting is
> forkCount=1/reuseForks=true'. Even when I explicitly specify these values
> within my Maven project's pom, I get the same build error that I mentioned
> originally within this thread. forkCount=1/reuseForks=false also doesn't
> work for me and fails my build with same sorts of error.
>
> I also don't wish to specify value of forkCount greater than 1, since I
> don't want my Maven project tests to run parallely. Because, most of my
> tests interact transactionally with a DB, and I believe parallel test
> execution would be problematic for my case.
>
> Any further thoughts would be useful to me.
>
>
>
>
> --
> Regards,
> Mukul Gandhi
>
