I agree with this. Nice clear write up of the problem and solution. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] On > Behalf Of Scott Hernandez > Sent: Thu, June 6, 2002 11:59 AM > To: 'NantDev' > Subject: [nant-dev] nant task and property inheritance > > > Okay, with the recent changes to the NAntTask we now have > something closer to what Ant does. But there are still some > differences. > > 1.) By default in Ant the child project has read-only access > (which means they are treated as user properties which cannot > be assigned to) to all the properties of the calling project. > NAnt by default does not give access to the parent properties > by default (like using <ant ... inheritAll='false'/>. > 2.) If <nant ... inheritall='true'/> then properties are > copied to new project (but not made read-only). > > > My take on this is that we should inherit by default and not > make them read-only (as we currently do). This differs from > Ant, but I never understood why inherited properties were > made read-only in the first place. I understand that you > wouldn't want the parent properties edited by the called > project, but as copies are made of the properties, I don't > see the harm in allowing the child project to make changes. > > > > > _______________________________________________________________ > > Don't miss the 2002 Sprint PCS Application Developer's > Conference August 25-28 in Las Vegas -- > http://devcon.sprintpcs.com/adp/index.cfm > > > _______________________________________________ > Nant-developers mailing list [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/nant-developers >
_______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
