But the I want the new functionality to be the default and the old functionality to be removed. This would cause ever statement people write to be:
<include buildfile="src/Project/Default.build" changebasedir="true"/> Vs <include file="src/Project/Default.build"/> I've always said we will be adding new breaking changes until 1.0 in order to get things right. What we could do is still support the buildfile attribute (I would also like to change that to just file) to do what people's existing files are expecting and issue a warning that that is a depreciated attribute. The buildfile attribute support would be removed at the 1.0 release. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Thursday, September 19, 2002 9:02 PM > To: '[EMAIL PROTECTED]'; > [EMAIL PROTECTED] > Subject: Re: [nant-dev] More info on the <include> task > > > > (Oops forgot to send this to the list) > > Gerry: > >If people still think the older <include> syntax is useful we could > >call this new task <import> > > What about a property: > <include changebasedir="true"/> > > Make it optional, and make the default false, so that it > doesn't break the current contract. > > Best, > Bill > > William E. Caputo > ThoughtWorks, Inc. > > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Nant-developers mailing list [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/nant-developers > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
