DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18700>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18700 Stange classpath problem [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |WONTFIX ------- Additional Comments From [EMAIL PROTECTED] 2003-04-07 10:03 ------- I understand your comments but I don't see that it is a 'big consistency problem'. There is a difference between not checking for the existence of a file and not knowing the file's name. If we were to defer the resolution of a property to the point of use, the path object could not be configured at all until use. Since the path elements take File arguments the File objects could not be constructed until the path is to be used whereupon it would have to be configured. We also would need to understand what is the point of use. You can argue that the <path> instance is a "use" of the properties and they therefore they should be resolved. If we decide to resolve on use of the path, we just shift the problem. Say there was another type that took a path as an argument. Should we defer the resolution of the path until the use of this new type. That might be possible. The rules of Ant configuration are currently that property resolution takes place at the point an object is configured, not where it is used. This is only an issue for datatypes (since they are likely to defined and then used - which doesn't happen for tasks) I can think of how to do it - it would involve leaving types as UnknownElements until a reference was fetched from the Project. That sort of change is pretty major - it would need some discussion on ant's dev list. I'm marking this as WONTFIX for now. If you want to discuss further, lets do it on ant dev.
