Hi there,
I've spent quite a while searching for a problem in our hudson integration code that boils down to unexpected results of commandLine.
One of our paramaters is named -logPath: and we had a path that includes Space characters (because the german version of windows calls the Users' path "Dokumente und Einstellungen").
So what we receive is an array that includes the following strings:
C:\Dokumente
und
Einstellungen\joachim\log.txt
No matter if I change the commandline to enclose the path with single or double quotes.
Here's the combinations I've tried so far - all with the same result:
abt.exe -iabt.icx -logPath:C\Dokumente und Einstellungen\joachim\log.txt
abt.exe -iabt.icx -logPath:'C\Dokumente und Einstellungen\joachim\log.txt' (which ends up with extra single quotes)
abt.exe -iabt.icx -logPath:"C\Dokumente und Einstellungen\joachim\log.txt"
I don't remember seeing this problem in VAST 8.0.3, but maybe on these machines we had other path configurations...
Do I really have to hand in these "Dokumen~" strings? In one case, I even can't because what gets actually handed in from the batch file is a reference to an environment variable which is filled by hudson... (-logPath:%WORKSPACE%)
Is there anything else I can do to make VAST understand commandLine parameters with Spaces in them?
Has the primitive VMprArgv changed in VAST 8.5?
Teh funny thing is: the very first parameter (my abt.exe start command) comes in correctly when it is put into double quotes in cmd.exe...
Joachim
--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/va-smalltalk/-/dATKiCm1COIJ.
To post to this group, send email to
[hidden email].
To unsubscribe from this group, send email to
[hidden email].
For more options, visit this group at http://groups.google.com/group/va-smalltalk?hl=en.
Locked
