What do folks think should be done, if anything, about this particular issue?
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5662 Nesting <ant> calls seems reasonable in componetized builds but having the first <ant> to set a property as a user property really ruins it for builds down the line because it can't be overridden using nested <property>. I'm particularly frustrated by the current behavior, but folks might be relying on the current functionality so changing it would affect them. Is this viewed as a bug? If so then changing it would be reasonable. Are there workarounds to this? Or perhaps a way to have the current functionality and had a switch such that properties being set from nesting under <ant> aren't set as user properties but rather regular properties? Thanks, Erik -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
