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 Import: Target Handling Bug ------- Additional Comments From [EMAIL PROTECTED] 2004-04-19 14:16 ------- ALAS, what you guys are describing results from the use of the project names to prefix the targets. I was SQUARELY against such a bad practice, which breaks encapsulation. With the model I proposed, no renaming took place, unless explicitly specified by the importER build, and the prefix used is local/private to the importER build. And I mean really private, i.e. somebody else importing that importER build never sees the prefixes used. This removes all ambiguities one build file at a time, without affecting anybody potentially using/importing that build down the line. At least I think this would have been a better scheme ;-) You guys are welcome to find edge cases that shows it wouldn't have ;-))). --DD --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
