Hi Scott, > Okay, with the recent changes to the NAntTask we now have something > closer to what Ant does. But there are still some differences.
To be honest, I had no clue about how ant does it, so I sorta implemented it as I thought would be most useful... > 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'/>. I did that on purpose as I did not know what it could break. It might need a few more tests (and I have a unit test in the works), but if you think it's OK, I'd see no problem in enabling it by default. > 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. That sounds very reasonable and I'd certainly support it... anyone else has any comments? -- Tomas Restrepo [EMAIL PROTECTED] _______________________________________________________________ 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
