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/23 18:36:15 UTC
[Bug 2687] - 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.7763 Mon Jul 23 09:36:15 2001
***************
*** 2,9 ****
| 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 |
+----------------------------------------------------------------------------+
--- 2,9 ----
| Wrong warnings "Property ${xxx} has not been set" in verbose mode |
+----------------------------------------------------------------------------+
| Bug #: 2687 Product: Ant |
! | Status: RESOLVED Version: 1.3 |
! | Resolution: FIXED Platform: All |
| Severity: Minor OS/Version: All |
| Priority: Other Component: Core tasks |
+----------------------------------------------------------------------------+
***************
*** 27,30 ****
}
--------------------------
The second call succeeds in resolving the property, but the first one issues the
! warning message.
--- 27,39 ----
}
--------------------------
The second call succeeds in resolving the property, but the first one issues the
! warning message.
!
! ------- Additional Comments From conor@cortexebusiness.com.au 2001-07-23 09:36 -------
! The problem is not in these threee lines as such but from the fact that
! properties object effectively reorders the values read in from the properties
! file. The result is creation of apparent forward references which cause the
! error get which get sorted out eventually.
!
! In any case, I have fixed this. Should only see real undefined property errors
! now.