[nant-dev] [ nant-Bugs-2697388 ] readonly property not readonly if already exist

[SourceForge.net <no...@so...>]

Bugs item #2697388, was opened at 2009-03-20 09:07
Message generated for change (Settings changed) made by georgesz
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=402868&aid=2697388&group_id=31650

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Core
Group: cvs
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: georgesz (georgesz)
Assigned to: Nobody/Anonymous (nobody)
>Summary: readonly property not readonly if already exist

Initial Comment:
Once a property has been defined read-write, if it is redefined readonly, the readonly attribute is ignored. I tested this with 0.85 and nant-0.86-nightly-2009-01-30. For example:

  <!-- This defines the property readwrite. -->
  <property name="p1" value="1"/>
  <echo message="${p1};${property::is-readonly('p1')}"/>
  <!-- This should redefine the property readonly, ... -->
  <property name="p1" value="2" readonly="true"/>
  <echo message="${p1};${property::is-readonly('p1')}"/>
  <!-- but it doesn't. The property can be set to '3'. -->
  <property name="p1" value="3"/>
  <echo message="${p1};${property::is-readonly('p1')}"/>

If this is by design, it should be noted in the documentation, for example in help/fundamentals/properties.html or help/tasks/property.html, as this behavior can be unexpected.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=402868&aid=2697388&group_id=31650