Sorry to pick up on this thread rather late but, am I correct in thinking that the include task can't be used within a target?
I have a situation where I would like to package an application for multiple clients. Certain targets use properties to configure various parts of the client installation. I'd also like to batch build each customer in turn, which relies on being able to set the properties within a target and repeat for each client. Unless I'm wrong in this scenario the <include> task wouldn't work, although <property file=".." /> may be useful? Darren Syzling mailto:[EMAIL PROTECTED] http://www.optial.com ------------------------------------------------ This message may contain information which is confidential or privileged. If you are not the intended recipient, please advise the sender immediately by reply e-mail and delete this message and any attachments without retaining a copy. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gert Driesen Sent: 14 October 2003 18:54 To: [EMAIL PROTECTED]; Marion Nalepa Subject: Re: [Nant-users] support for property files ? ----- Original Message ----- From: "Marion Nalepa" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, October 14, 2003 8:39 PM Subject: [Nant-users] support for property files ? > I'm wondering if there is an equivalent ability in NAnt to > Ant's property file feature: > > Specifically, in Ant you can load properties from an external > file such as: > > <property file="build.properties" /> > > where this file contains name/value pairs like: > > prop1=value1 > prop2=value2 > ... > > This is immensely useful to allow for a universal build file to > be constructed, with each developer only having to edit an > external properties file to tailor the build to his/her individual > system. in NAnt we just an include task which loads a "build file" containing only property declarations ... eg. <include buildfile="build.properties" /> and build.properties would then look like this : <project name="build-properties"> <property name="prop1" value="value1" /> <property name="prop2" value="value2" /> </project> Hope this helps, Gert ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users ------------------------------------------------------- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/ _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
