ivy:buildnumber taking over 10 minutes to run, and increasing as version number increases

[Krishna Rao]

Hi all,

we're using Ivy to publish a jar build to Artifactory. However, the ant
task to calculate the next version number is taking a surprisingly long
amount of time. I ran this ant task in debug mode and it shows that ivy
seems to iterate through all published jars and other build outputs, i.e.:

***
[ivy:buildnumber] using public to list all in http://
<repository.url>/libs-release/com/example/module1/0.22

[ivy:buildnumber] ApacheURLLister found URL=[http://
<repository.url>/libs-release/com/example/module1/0.22/ivy-0.22.xml]

***
for every version number, and for a variety of file types!

Any ideas what might be set up wrong? All the config I think is relevant is
below.

Cheers,

Krishna


The target is defined as:

***
<target name="version" description="Gets the next version number from Ivy">
      <ivy:buildnumber organisation="com.example" module="module1"
revision="${jar.version}" />
      <echo>Version number: ${ivy.revision} -> ${ivy.new.revision}</echo>
  </target>
***

ivysettings.xml contains:

***
<ivy-settings>
    <properties file="localIvy.props"/>
    <properties file="ivy.props" override="false"/>
    <caches defaultCacheDir="/tmp/ivy-cache" />

    <settings defaultResolver="main" />
    <!--Authentication required for publishing (deployment). 'Artifactory
Realm' is the realm used by Artifactory so don't change it.-->
    <credentials host="${repository.host}" realm="Artifactory Realm"
username="${repository.username}" passwd="${repository.password}" />
    <resolvers>
        <chain name="main">
            <url name="public" m2compatible="true">
                <artifact
pattern="${repository.virtual.url}/[organization]/[module]/[revision]/[artifact]-[revision].[ext]"/>
                <ivy
pattern="${repository.virtual.url}/[organization]/[module]/[revision]/ivy-[revision].xml"
/>
            </url>
        </chain>
        <url name="publish" m2compatible="true">
            <artifact
pattern="${repository.local.url}/[organization]/[module]/[revision]/[artifact]-[revision].[ext]"/>
            <ivy
pattern="${repository.local.url}/[organization]/[module]/[revision]/ivy-[revision].xml"
/>
        </url>
        <filesystem name="local-ivy" m2compatible="true" force="false"
local="true">
            <artifact
pattern="${ivy.default.ivy.user.dir}/local/[organisation]/[module]/[revision]/[artifact]-[revision].[ext]"/>
            <ivy
pattern="${ivy.default.ivy.user.dir}/local/[organisation]/[module]/[revision]/ivy-[revision].xml"
/>
        </filesystem>
  </resolvers>
</ivy-settings>
***

And finally, there is an version.props that contains something like:
"jar.version=6.0"