ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 23278] New: - Project.setName() does not replaceProperties()
Date Fri, 19 Sep 2003 17:28:17 GMT
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=23278>.
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=23278

Project.setName() does not replaceProperties()

           Summary: Project.setName() does not replaceProperties()
           Product: Ant
           Version: 1.5
          Platform: All
        OS/Version: Other
            Status: UNCONFIRMED
          Severity: Minor
          Priority: Other
         Component: Core
        AssignedTo: dev@ant.apache.org
        ReportedBy: gregb+apachebug@blackholio.dyndns.org


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?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message