Can't use -Dmaven.repo.local=tmp in multi-module reactor when
useSystemClassLoader=false
----------------------------------------------------------------------------------------
Key: SUREFIRE-499
URL: http://jira.codehaus.org/browse/SUREFIRE-499
Project: Maven Surefire
Issue Type: Bug
Components: process forking
Affects Versions: 2.4.3
Reporter: Dan Fabulich
At Redfin, we often launch builds with -Dmaven.repo.local=tmp (that is,
temporarily put the local repo in the root of the build dir) to guarantee
reproducibility. In a reactor build, we launch the sub-process and modify
user.dir to be the dir of the leaf projects.
When useSystemClassLoader=false, the IsolatedClassLoader thinks that the local
repo is in "parent/child/tmp" rather than "parent/tmp"; as a result, the ICL
fails to load any classes out of the local repository.
The fix should be to make the classpath absolute rather than passing relative
paths to the launched process. This might be a Maven core bug, or it might be
possible to handle it in the plugin.
--
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
