Maven 2.x Ant Tasks

I deploy with:

<artifact:deploy file="${dist.home}/${app.name}.${jar.dist.suffix}">
<remoteSnapshotRepository refid="jar.repo.cu" />
<pom refid="jar.pom" />
</artifact:deploy>

The repository's maven-metadata.xml has:
<metadata>
<groupId>edu.cornerstone.portal.eforms</groupId>
<artifactId>eforms</artifactId>
<version>1.0-SNAPSHOT</version>
<versioning>
<snapshot>
<buildNumber>89</buildNumber>
</snapshot>
<lastUpdated>20051025124212</lastUpdated>
</versioning>
</metadata>

The local repository of the box that deployed the artifact has the same
contents in maven-metadata-remote.xml

However, when other users download the artifact from the repository
their maven-metadata-remote.xml does not have any <versioning> tags.

Thanks,
Dave

Brett Porter wrote:

>> How were the snapshots deployed? The mechanism now relies on the
>> correct management of maven-metadata.xml.
>>
>> - Brett
>>
>> On 10/24/05, Dave Brondsema <dave@brondsema.net> wrote:
>>
>
>>>>I have an ant task to download all the jar artifacts but it won't
>>>>download new SNAPSHOTs if there is already a snapshot in the local user
>>>>repository.
>>>>
>>>>The relavant parts of my ant build file:
>>>>
>>>><artifact:remoteRepository id="jar.repo.cu" url="${jar.repo.cu.url}"
>>>>layout="default">
>>>> <snapshots updatePolicy="always" />
>>>></artifact:remoteRepository>
>>>>
>>>><artifact:dependencies verbose="true" useScope="compile"
>>>>filesetId="jar.libs.fileset">
>>>> <pom refid="jar.pom" />
>>>> <remoteRepository refid="jar.repo.suppl" />
>>>> <remoteRepository refid="jar.repo.cu" />
>>>> <remoteRepository refid="jar.repo.m2" />
>>>></artifact:dependencies>
>>>>
>>>>
>>>>
>>>>And the dependencies that are declared like this:
>>>><dependency>
>>>> <groupId>edu.cornerstone.portal.jsf-utilities</groupId>
>>>> <artifactId>jsf-utilities</artifactId>
>>>> <version>1.0-SNAPSHOT</version>
>>>></dependency>
>>>>
>>>>
>>>>According to my apache logs (which serves the repository at
>>>>${jar.repo.cu.url}) maven never accesses the repository.

could this have to do with missing metadata on the remote repository, as in the case of a maven1 repository?

I'm using an internal m2 repository. And the repository does have a maven-metadata.xml with <versioning>

I think this is a duplicate

since the beginning of the year, new version of Maven Ant Tasks have been released that fix a lot of issues.
Can you check if this problem is still present with Maven Ant Tasks 2.0.7?

no news, no test case
I suppose this is an old problem already fixed in 2.0.7