This just happened to us after going to 1.6. Will there be some kind of fix in ccnet, or do we have to rewrite all config-files?
I don't mind rewriting the files, but forcing all arguments on the same row makes the configuration harder to read. We have some horrible nant-tasks that require 7-8 arguments, and putting these arguments on the same row makes the config-file almost unreadable... /Fredrik On Feb 15, 7:55 pm, "Craig Sutherland" <[email protected]> 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 > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > > Behalf Of östen petersson > Sent: Tuesday, 15 February 2011 1:18 a.m. > To: ccnet-user > Subject: [ccnet-user] Re: CCNet project works fine in 1.5 but not in 1.6 > > @ johnny I had the same problem as you but with some other tool - the > quickfix was to set all the args on one line - harder on the brain but it > works > > On Feb 7, 8:17 pm, "Craig Sutherland" <[email protected]> > wrote: > > Hi John, > > > I've managed to track down (roughly) where the problem is happening. > > It appears that the changes to the pre-processor affect whether > > whitespaces are being trimmed or not. In 1.5 the new lines and spaces > > where being trimmed, in 1.6 they are not. Consequently NAnt does not like > the build args. > > > Unfortunately I don't know why this was changed or what effect it will > > have if we change back. I will keep looking to see if I can figure out > > how to revert to the previous behaviour. > > > PS, don't worry about attaching the logs - the config is the main part > > I needed :-) > > > Craig > > > -----Original Message----- > > From: [email protected] [mailto:[email protected]] > > On > > > Behalf Of JohnnyV > > Sent: Tuesday, 8 February 2011 12:31 a.m. > > To: ccnet-user > > Subject: [ccnet-user] Re: CCNet project works fine in 1.5 but not in > > 1.6 > > > Hi Craig, here they are. > > > <cruisecontrol xmlns="http://thoughtworks.org/ccnet/1/6";> > > > <project name="JohnTest2" > > > <tasks> > > <nant> > > <executable>C:\Program Files (x86)\nant-0.85\bin\nant.exe</ > > executable> > > <!-- This works in CCNet 1.6.7981.1 > > <buildArgs>-D:myprop1=test123 -D:myprop2=test456</buildArgs> > > --> > > <!-- This works in CCNet 1.5.7256.1 but not in CCNet > > 1.6.7981.1 --> > > <buildArgs> > > -D:myprop1=test123 > > -D:myprop2=test456 > > </buildArgs> > > <!-- --> > > <buildFile>D:\Build Area\John Test\Scripts\build.build</ > > buildFile> > > <targetList> > > <target>target1</target> > > </targetList> > > </nant> > > </tasks> > > </project> > > > </cruisecontrol> > > > NANT: > > <?xml version="1.0"?> > > > <project name="build" xmlns="http://nant.sf.net/release/0.85/nant.xsd"; > > > <echo message="DEBUGGING START" /> > > <echo message="project::get-name='${project::get-name()}'" /> > > <echo > > message="project::get-default-target='${project::get-default- > > target()}'" /> > > <echo message="target::exists('target1')='$ > > {target::exists('target1')}'" /> > > <echo message="DEBUGGING END" /> > > > <target name="target1"> > > <echo message="TARGET '${target::get-current-target()}' > > STARTED" /> > > <echo message="Starting build.build for project > > '${CCNetProject}' at ${datetime::now()}" /> > > </target> > > > </project> > > > I'm new to Google Groups - I thought there would be a way to attach > > files, but I can't see any. The log files are a bit too long to just paste > here. > >
