You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by bu...@apache.org on 2001/07/19 15:26:16 UTC
[Bug 2687] New: - Wrong warnings "Property ${xxx} has not been set" in verbose mode
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2687
*** shadow/2687 Thu Jul 19 06:26:16 2001
--- shadow/2687.tmp.28371 Thu Jul 19 06:26:16 2001
***************
*** 0 ****
--- 1,30 ----
+ +============================================================================+
+ | Wrong warnings "Property ${xxx} has not been set" in verbose mode |
+ +----------------------------------------------------------------------------+
+ | Bug #: 2687 Product: Ant |
+ | Status: NEW Version: 1.3 |
+ | Resolution: Platform: All |
+ | Severity: Minor OS/Version: All |
+ | Priority: Other Component: Core tasks |
+ +----------------------------------------------------------------------------+
+ | Assigned To: ant-dev@jakarta.apache.org |
+ | Reported By: peter@pholzwarth.de |
+ | CC list: Cc: |
+ +----------------------------------------------------------------------------+
+ | URL: |
+ +============================================================================+
+ | DESCRIPTION |
+ when launching build with the -verbose switch, the warning "Property
+ ${xxx} has not been set" appears wrongly, when a property is used in a property
+ file that is defined in the same property file. The reason for this seem to be
+ these lines in taskdefs/Property.java:
+ --------------------------
+ if (!resolved) {
+ value = ProjectHelper.replaceProperties(project, value,
+ project.getProperties());
+ value = ProjectHelper.replaceProperties(project, value, props);
+ props.put(name, value);
+ }
+ --------------------------
+ The second call succeeds in resolving the property, but the first one issues the
+ warning message.