[
https://issues.apache.org/jira/browse/SUREFIRE-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliotte Rusty Harold resolved SUREFIRE-1304.
---------------------------------------------
Resolution: Fixed
Sounds like this has been fixed. Perhaps reopen if it can still be reproduced.
Keep in mind that a VM crash is almost by definition a VM bug, not a bug in
Maven. Pure Java code should not be able to crash the VM, no matter what it
does. Unless maybe it happens when we shell out to a CLI tool?
> VM crash when using reportsDirectory pointing to parent module and maven
> parallel build
> ---------------------------------------------------------------------------------------
>
> Key: SUREFIRE-1304
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1304
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
> Affects Versions: 2.19.1
> Environment: windows 7 x86 64
> Reporter: Jérôme Van Der Linden
> Priority: Critical
> Fix For: Backlog
>
>
> In my parent pom, i've configured the surefire plugin with
> {{<reportsDirectory>$\{basedir}/../surefire-reports</reportsDirectory>}}
> So that all reports go to the parent folder (i have one parent module with n
> submodules just below). I need to centralize all reports from all modules in
> order to use another tool on them.
> If i do this and use *mvn -T 1C* to use parallel build, i have the following
> error :
> {{The forked VM terminated without saying properly goodbye. VM crash or
> System.exit called}}
> If i remove the reportsDirectory, no more problem, but all reports stay in
> submodules... I could use an ant task to copy files at the end of tests but
> it sucks...
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
