https://issues.apache.org/bugzilla/show_bug.cgi?id=18732
Nick Silkey <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] Version|1.7.0 |1.8.1 --- Comment #6 from Nick Silkey <[email protected]> 2010-06-03 17:03:50 EDT --- Yeah, this behavior is bothersome and (imho) a bug. I have this in foo.properties: base.path=/base/path deploy.app=foo deploy.path=${base.path}/${deploy.app} I want this at runtime: base.path=/base/path deploy.app=foo deploy.path=/base/path/foo If the Ant xml includes <property file="foo.properties" />, nested properties listed in foo.properties are expanded. If -propertyfile is used, either from the cli @ invocation (ant -f foo.xml target -propertyfile foo.properties) or via ANT_ARGS, the nested properties (i.e. ${deploy.path} do not expand/enumerate/etc. FWIW, running Ant in debug shows that properties slurped in via -propertyfile invocations are set to 'ro project property'. In debug when you call to a property file directly via <property /> in your Ant XML, these are set to 'project property'. This issue manifests in the current release (1.8.1). And nothing in the docs seems to indicate that Ant should behave differently at runtime whether one sets properties via <property ... />, -propertyfile, or -Dproperty.foo, etc. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
