Scenario: pass ant commandline parameter "-propertyfile <filename>" property file contains: foo = bar build.xml <project name="${foo}" default="baz"> At the time that Project.setName() is invoked by ProjectHelperImpl, the project's properties hashtable has already been initialized and the specified propertyfile has been loaded. Despite this, the project name property contains "${foo}" instead of "bar", as it would, if Project.replaceProperties() was called. Query: should this also be applied to Project.setDefault() as well?
There are certain attributes that don't get properties expanded. In particular, the attributes of target and project do not get expanded. At least in the case of <target>, this is intended.
I'd day it is intended for <project> as well. I don't think the project name should be controlled through a property. What would be the usecase for that?
Freedem