[
http://jira.codehaus.org/browse/SUREFIRE-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_88897
]
Jan Hoeve commented on SUREFIRE-296:
------------------------------------
I do not have a global JAVA_HOME environment variable.
Instead (for some reasons) i set JAVA_HOME in the mvn script:
JAVA_HOME="/build/buildserver/jdk1.5.0"
That worked in surefire 2.2. Did SUREFIRE-135 changed the forking process in a
way my method fails?
> Since version 2.3 surefire fails to run on linux
> ------------------------------------------------
>
> Key: SUREFIRE-296
> URL: http://jira.codehaus.org/browse/SUREFIRE-296
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.3
> Environment: linux, suse 8, java 1.5, maven 2.0.4
> Reporter: Jan Hoeve
> Priority: Blocker
> Attachments: surefire.txt
>
>
> This night the surefire plugin has been updated to version 2.3
> When i now execute "mvn test" it fails with the following error:
> java.io.IOException: /build/buildserver/jdk1.5.0/jre/bin/java: cannot execute
> For more information, see the attached log
> Also: on windows there is no problem, it only occurs on linux.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
