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 16934] New: - BuildNumber task does not set property correctly
Date Mon, 10 Feb 2003 17:15:46 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=16934>.
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=16934

BuildNumber task does not set property correctly

           Summary: BuildNumber task does not set property correctly
           Product: Ant
           Version: 1.5.1
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Core tasks
        AssignedTo: dev@ant.apache.org
        ReportedBy: rich.naylor@active-endpoints.com


When the BuildNumber task is executed, it sets a build.number property which 
can then be referenced from within the ant build file. Unfortunately, it is 
setting it to the previous build number before it was incremented and not the 
new build number. Is this performing as designed or truly an error. I really 
need to have the new build number, and I'm currently using some javascript code 
to work around this. Thanks

Mime
View raw message