DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=28444>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=28444 ------- Additional Comments From [EMAIL PROTECTED] 2005-02-01 17:34 ------- Adding an "optional if no conflict" prefix is insufficient. My scenario is a tad different: I've got a 'framework' buildfile that imports local rules. I require the local rules to define certain targets, so I know that e.g. "local_rules.clean" exists (if it doesn't exist, an abort is desirable behavior). There is also a automatically generated portion in a separate file. I know what the filename/projectname is, so that's fine. But when developing a new target-set, not all of the local rules files or framework files may be totally up-to-date. This only becomes irksome when one component, that *KNOWS* someproject.sometarget exists, explodes because "someproject.sometarget" is not defined--although "sometarget" is. I don't know how the internals of import work, but I cannot imagine that adding two namespace entries is a performance consideration of any kind. Please make this behavior consistent. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
