"Forked Java VM exited abnormally" when running "Test File" on Maven project

[Halvor Platou]

I’m not sure if this is an issue with NetBeans/Maven or maven-surefire-plugin, but when I select “Test File” without code changes in source(only test source), the “java.library.path” used by surefire-plugin is wrong.

There are a few conditions for this to happen:

<![if !supportLists]>1. <![endif]>pom.xml contains configuration of maven-surefire-plugin:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>2.8.1</version>
<configuration>
<argLine>-Djava.library.path="${project.build.directory}"</argLine>
</configuration>
</plugin>
<![if !supportLists]>2. <![endif]>The “${project.build.directory}” contains a white-space in the path


When select “Test File” without code-changes in the source it seems that NetBeans somehow adds the class-file of the test-file to java.library.path without actually running maven. Is this correct? It also seems it will try to merge java.library.path with what sure-fire-plugin has configured, without taking into account that this path could contain a white-space.

Anyone know how this actually work?

Halvor Platou
Technical Coordinator CyberSea Technology
Marine Cybernetics
Vestre Rosten 77, Trondheim, Norway
www.marinecyb.com