Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 1.0-alpha-4
-
Component/s: None
-
Labels:None
-
Environment:Windows XP, Continuum SVN snapshot, Maven 2 SVN snapshot
-
Complexity:Intermediate
-
Number of attachments :
Description
ok, I have been noticing build failures on Integration tests for sometime now. On playing around with the PATH variables and looking at plexus DefaultExecutableResolver source, i noticed the following:
a) plexus.system.path was being set to '' (empty string) on my system even though the PATH is set to include all reqd. executables. The PATH variable had values with space (ex: c:\Program Files\...)
b) On running integ. tests with -Dplexus.system.path=%PATH% set on command line, the spaces in the path variable were not being handled correctly, seems like the 'path list' used to resolve executables is being set up incorrectly. I am not sure if this is better reported as an issue on Plexus JIRA or here.
c) on running integ. tests with -Dplexus.system.path="%PATH%", the path list is being build up properly and executables are getting resolved. Not sure where this property is being set up in first place. In case, this being setup and passed via build script, would it be a good idea to have double quotes around PATH?
already fixed