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 19737] - <loadproperties> does not load updated file in same target
Date Thu, 08 May 2003 08:52:02 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=19737>.
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=19737

<loadproperties> does not load updated file in same target

mhilpert@gmx.de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |



------- Additional Comments From mhilpert@gmx.de  2003-05-08 08:52 -------
but the build.number is not set to the current value. here's a test case:

--------
    <target name="build.number++" description="increase build number">
        <echo message="current bn=${build.number}"/>
        <!-- increase build number in file build.number: -->
        <buildnumber file="${java}${fs}build.number"/>
        <echo message="next bn=${build.number}"/>
        <!-- get new build number: -->
        <loadproperties srcfile="${java}${fs}build.number"/>
        <echo message="new bn=${build.number}"/>
    </target>
-------

output is:

-------
build.number++:
        [echo] current bn=${build.number}
        [echo] next bn=9
        [echo] new bn=9
-------

although the build.number file has a build.number property value of 10! i run 
this a dozen times and the output is always 1 lower than the value in the 
build.number file.

Mime
View raw message