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=11585>. 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=11585 The Replace Task ignores properties with multiline replacements ------- Additional Comments From [EMAIL PROTECTED] 2003-07-31 18:37 ------- This is a troublespot. Most tasks that dont expand properties inline do it because they are broken. Moving to expansion runs the risk of breaking something. I remember how before I could fix <telnet> to expand, we had to change property expansion ant-wide so that single $ signs werent being autostripped. 1. Are there any use cases we can imagine where people dont want property expansion? 2. Do any well known ant or third party tools do it? 3. if we go to auto-expansion, and some third party task retains its replaceProperties call, what are the consequences. Point (3) worries me. We could break 3rd party tasks between ant versions. Better, perhaps, to have a new introspection point. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
