[ http://jira.codehaus.org/browse/CONTINUUM-303?page=all ]
Emmanuel Venisse closed CONTINUUM-303:
--------------------------------------
Assign To: Emmanuel Venisse
Resolution: Fixed
Fix Version: 1.0-alpha-4
already fixed
> property 'plexus.system.path' is being set to empty and results in maven, m2
> and ant executables to be unresolved
> -----------------------------------------------------------------------------------------------------------------
>
> Key: CONTINUUM-303
> URL: http://jira.codehaus.org/browse/CONTINUUM-303
> Project: Continuum
> Type: Bug
> Environment: Windows XP, Continuum SVN snapshot, Maven 2 SVN snapshot
> Reporter: Rahul Thakur
> Assignee: Emmanuel Venisse
> Fix For: 1.0-alpha-4
>
>
> 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?
--
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
