Thanks guys, your suggestions did the trick. >-----Original Message----- >From: Guy Metz [mailto:[EMAIL PROTECTED] >Sent: Wednesday, October 25, 2006 8:20 AM >To: Steve Valaitis; nant-users@lists.sourceforge.net >Subject: RE: [NAnt-users] <nant> task not passing properties. > >Are the properties that you are trying to reset defined in your common >include file? If they are then the value would by default be reset to >the value in the include. We have a similar situation where we want the >properties to have one value by default in all of the component builds >but be able to switch the value globally in a master build >file. What we >do is the set the "overwrite" attribute for the properties in >the common >include to false. This effectively turns off the property set if it's >already defined as would using the "if"/"unless" attributes but with >less typing. >Hope this helps > >> -----Original Message----- >> From: [EMAIL PROTECTED] [mailto:nant-users- >> [EMAIL PROTECTED] On Behalf Of Steve Valaitis >> Sent: Wednesday, October 25, 2006 12:08 AM >> To: nant-users@lists.sourceforge.net >> Subject: [NAnt-users] <nant> task not passing properties. >> >> I have a buildfile(default) with the following in a target: >> >> <nant target="${build.target}"> >> <buildfiles> >> <include name="fs.build"/> >> <include name="pa.build"/> >> </buildfiles> >> </nant> >> >> According to the docs for <nant>, all of the current property values >> should be automatically passed to the build files. I assumed it would >be >> similar to -D:prop=value, but the build files process without any >change >> to their properties. >> >> I then tried adding the following to my nant task, thinking that this >> would make things work, but I still get the same result: >> >> <properties> >> <property name="fresh.build" value="${fresh.build}" >overwrite="true" >> readonly="true"/> >> <property name="need.checkout" value="${need.checkout}" >> overwrite="true" readonly="true"/> >> </properties> >> >> The only way I have gotten things to work is by calling an exec task >for >> each of the build files, and manually constructing the arguments to >pass >> over. This seems somewhat brittle, and hackish. Is this >behavior to be >> expected? Am I doing something wrong? >> >> All of the build files include a common.build buildfile that has some >> properties declared at the global level. Would this be causing the >> problem, and if so, can I get around it? >> >> Thanks, >> Steve >> >> >--------------------------------------------------------------- >--------- >- >> Using Tomcat but need to do more? Need to support web services, >security? >> Get stuff done quickly with pre-integrated technology to >make your job >> easier >> Download IBM WebSphere Application Server v.1.0.1 based on Apache >Geronimo >> >http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&d >at=121642 >> _______________________________________________ >> NAnt-users mailing list >> NAnt-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/nant-users > >
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ NAnt-users mailing list NAnt-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users
