<span class="since">since 1.4</span> The buildnumber task is similar to the ant buildnumber task, except that it uses ivy repository to find what is the latest version and calculate a new one for you. When called it sets four properties according to what has been found. These properties are: <ul> <li>ivy.revision</li> the last revision found in the repository <li>ivy.new.revision</li> the new revision calculated from the last one (see below) <li>ivy.build.number</li> the build number found in the repository <li>ivy.new.build.number</li> the new build number calculated from the last one, usually with +1 </ul> build numbers are always numbers (composed of digit characters only). ivy.revision can be not set if no revision was found ivy.build.number can be not set if no revision was found or if no number was found in it ivy.new.build.number can be not set if the default new revision to use when no revision is found do not contain any number The new revision is calculated using a somewhat complex to explain but very easy to use algorithm, depending on which latest version you asked. Indeed you can ask for a new revision based upon the latest found for a particular prefix (the revision asked), then the new revision will be the one immediately after with only the prefix in common. If no prefix is set the very latest version is searched. Examples (suppose the latest version of the module is 1.3.1): <table> <tr><th>revision asked</th><th>ivy.revision</th><th>ivy.new.revision</th><th>ivy.build.number</th><th>ivy.new.build.number</th></tr> <tr><td>1.3</td><td>1.3.1</td><td>1.3.2</td><td>1</td><td>2</td></tr> <tr><td>1</td><td>1.3.1</td><td>1.4</td><td>3</td><td>4</td></tr> <tr><td>2</td><td>not set</td><td>2.0</td><td>not set</td><td>0</td></tr> <tr><td></td><td>1.3.1</td><td>1.3.2</td><td>1</td><td>2</td></tr> </table> Note that when asking for revision 1, you can get a revision 10.0. To avoid that you can use 1. as revision asked, but in this case ivy won't find revision 1 if its the latest one, and it will thus give 1.0 as new revision. The solution to this problem is to use versions with always the same number of parts (for instance 1.0.0 instead of 1). <table class="ant"> <thead> <tr><th class="ant-att">Attribute</th><th class="ant-desc">Description</th><th class="ant-req">Required</th></tr> </thead> <tbody> <tr><td>organisation</td><td>the organisation of the module for which a new build number should be calculated</td> <td>Yes</td></tr> <tr><td>module</td><td>the name of the module for which a new build number should be calculated</td> <td>Yes</td></tr> <tr><td>branch</td><td>the branch of the module for which a new build number should be calculated</td> <td>No, defaults to the default branch for this module</td></tr> <tr><td>revision</td><td>the revision prefix for which a new build number should be calculated</td> <td>No, defaults to no prefix (will find the latest version)</td></tr> <tr><td>default</td><td>the default revision to assume when no revision prefix is asked and no revision is found</td> <td>No, defaults to 0</td></tr> <tr><td>defaultBuildNumber</td><td>the default build number to use for the first revision</td> <td>No, defaults to 0</td></tr> <tr><td>revSep</td><td>the revision separator to use when no matching revision is found, to separate the revision prefix from the build number</td> <td>No, defaults to '.'</td></tr> <tr><td>prefix</td><td>the prefix to use for the property names set (will be <i>prefix</i>.revision, <i>prefix</i>.new.revision, ...)</td> <td>No, defaults to ivy</td></tr> <tr><td>settingsRef</td><td><span class="since">(since 2.0)</span> A reference to the ivy settings that must be used by this task</td><td>No, 'ivy.instance' is taken by default.</td></tr> </tbody> </table> <h1>Examples</h1> Here is how it can be used (suppose 1.3.1 is the latest version of ivy in the repository): <code type="xml"> <ivy:buildnumber organisation="apache" module="ivy" /> </code> will set 1.3.1 as revision, 1.3.2 as new revision, 1 as build number and 2 as new build number <hr/> <code type="xml"> <ivy:buildnumber organisation="apache" module="ivy" revision="1.3" /> </code> will set 1.3.1 as revision, 1.3.2 as new revision, 1 as build number and 2 as new build number <hr/> <code type="xml"> <ivy:buildnumber organisation="apache" module="ivy" revision="1.2" /> </code> will set 1.2 as revision, 1.2.1 as new revision, no build number and 1 as new build number <hr/> <code type="xml"> <ivy:buildnumber organisation="apache" module="ivy" revision="1." /> </code> will set 1.3.1 as revision, 1.4 as new revision, 3 as build number and 4 as new build number <hr/> <code type="xml"> <ivy:buildnumber organisation="apache" module="ivy" revision="3." /> </code> will set no revision, 3.0 as new revision, no build number and 0 as new build number <hr/> <code type="xml"> <ivy:buildnumber organisation="apache" module="ivy" revision="1.4-RC" defaultBuildNumber="1" revSep=""/> </code> If called while no release candidate is in the repository, will set ivy.revision to 1.4-RC1. Then it will increment each time, 1.4-RC2, 1.4-RC3, and so on.