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=9481>. 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=9481 Add a "prefix" attribute to ExpandProperties filter to allow limiting expansion to certain properties. ------- Additional Comments From [EMAIL PROTECTED] 2002-05-29 11:12 ------- 1. I bet you don't mean "case" as in "uppercase" and "lowercase". ;) The particular use case I've encountered is Java policy files, which can and often do contain system properties (which I'm not familiar with enough, as demonstrated by my previous comment to bug #5842 - thanks for the ${user.dir} tip, Stefan). I do not want the system properties to be expanded, since I'm not necessarily going to run my app on the same platform I'm building it on. Also, Unix shell scripts could also be using ${} constructs which may coincidentally contain user/system properties and thus be accidentally expanded. 2. Umm, I didn't understand your question. You mean that multiple prefix-attributes (well, they'd be nested elements, then) should be allowed and the properties expanded? 3. I actually ment it to be used similarly to "prefix" attribute on properties, after all we are expanding properties here. In my particular use case, I've read platform dependent properties from a file and want to read them again (possibly from another file) and assign them a prefix, and then expand the prefixed properties (and ONLY the prefixed properties in order to not mess up a policy file and shell scripts) in my "template files". -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
