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=7221>. 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=7221 change property expansion code to pass $ as is when not followed by $ or { Summary: change property expansion code to pass $ as is when not followed by $ or { Product: Ant Version: 1.1 Platform: All OS/Version: Other Status: NEW Severity: Enhancement Priority: Other Component: Core AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] If we tweak the property expander to return a $ when a property is not the next itme on the string (peek()='{') then users wont get confused about $ being dropped. For backwards compatiblity, we need to handle $$ by replacing it with $. Yes, that will cause forwards confusion; I look forward to the first 'two $$ signs are replaced by $' bugrep -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
