I really have a problem with this request. I am a believer on inmutable properties. Even though there was a vote on allowing changing properties, I think that is the wrong thing to do. The only place I see for modifying the values of properties in when executing the <ant*> family of tasks. Those taks create a new "project environment" and as such are cleanly defining a new context for property values. In those tasks, I would agree, we need the ability to specify that some property, defined in the project caller, must be made undefined at the begining of the project callee.
Of course, I am of the opinion the the current inheritance rules for properties in subprojects need to be revised, and maybe this issue should be part of it. Comments, Jose Alberto > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Sunday, May 13, 2001 10:31 PM > To: [EMAIL PROTECTED] > Subject: [Bug 1732] Changed - Add ability to remove a project property > > > http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1732 > > *** shadow/1732 Sun May 13 14:29:39 2001 > --- shadow/1732.tmp.12912 Sun May 13 14:30:41 2001 > *************** > *** 4,10 **** > | Bug #: 1732 Product: Ant > | > | Status: NEW Version: 1.3 > | > | Resolution: Platform: All > | > ! | Severity: Normal OS/Version: All > | > | Priority: Medium Component: Core > tasks | > > +------------------------------------------------------------- > ---------------+ > | Assigned To: [EMAIL PROTECTED] > | > --- 4,10 ---- > | Bug #: 1732 Product: Ant > | > | Status: NEW Version: 1.3 > | > | Resolution: Platform: All > | > ! | Severity: Enhancement OS/Version: All > | > | Priority: Medium Component: Core > tasks | > > +------------------------------------------------------------- > ---------------+ > | Assigned To: [EMAIL PROTECTED] > | >
