Hi,
We're seeing a related issue, though it's basically the opposite problem in
that whitespace is being stripped under 1.6 when it wasn't in 1.5. We have
various bits of config files that look something like this:
<exec executable="foo.bat"
baseDirectory="$(myBaseDir)"
buildArgs="$(myPort) $(myUser) $(myPassword) $(myWorkspace)"
description="Foo" />
Unfortunately under 1.6 it has started stripping out the spaces in the
generated buildArgs, ie. as if we'd written
"$(perforceArtServerPort)$(perforceArtUser)$(perforceArtPassword)$(perforceArtWorkspace)"
instead. The only way I could get it to work was to rewrite it like this:
<exec>
<executable>foo.bat</executable>
<baseDirectory>$(myBaseDir)</baseDirectory>
<buildArgs>$(myPort) $(myUser) $(myPassword)
$(myWorkspace)</buildArgs>
<description>Foo</description>
</exec>
I'm not really sure why that should make any difference though!
As 1.6 sadly didn't provide the change I'd hoped for after reading the build
notes anyway, we've simply rolled back to 1.5 for now.
On Tuesday, February 15, 2011 6:55:25 PM UTC, Craig Sutherland wrote:
Just a quick update on this - it is due to changes in the pre-processor. In
> 1.5 it was (incorrectly) stripping out whitespace, which made it impossible
> to put newlines, double spaces, etc. in an argument. In 1.6 this problem
> was
> fixed but now it breaks older configurations :-(
>
> We are looking into what we can do about this and hopefully will come up
> with a solution soon,
>
>
> Craig
>
>
