You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@archiva.apache.org by to...@gi-de.com on 2008/05/26 11:55:44 UTC
Latest deployed SNAPSHOT version not downloaded
Hi,
I use Maven 2.0.9 and Archiva 1.0.2, Archiva manages my own "internal" and
"snapshot" company repo.
Since a couple of days, I have problems with downloading SNAPSHOT versions
from my Archiva Managed Repo.
Archiva (or Maven?) is not downloading the latest version, the download
takes the previous version before the latest SNAPSHOT (Latest minus 1).
In the Repo I can see
D:\Archiva\repositories\snapshots\com\gide\logging\gide-revision-logging\3.1.0-SNAPSHOT
gide-revision-logging-3.1.0-20080421.164814-1.jar
gide-revision-logging-3.1.0-20080421.171134-2.jar
gide-revision-logging-3.1.0-20080422.131203-3.jar
gide-revision-logging-3.1.0-20080506.124327-4.jar
gide-revision-logging-3.1.0-SNAPSHOT.jar
When I do a local build, the dependency is resolved to
gide-revision-logging-3.1.0-20080506.124327-4.jar and
gide-revision-logging-3.1.0-SNAPSHOT.jar
in my \localrepo, being gide-revision-logging-3.1.0-SNAPSHOT.jar the same
as gide-revision-logging-3.1.0-20080506.124327-4.jar
the "maven-metadata.xml" is like:
<?xml version="1.0" encoding="UTF-8"?>
<metadata>
<groupId>com.gide.logging</groupId>
<artifactId>gide-revision-logging</artifactId>
<version>3.1.0-SNAPSHOT</version>
<versioning>
<snapshot>
<buildNumber>4</buildNumber>
<timestamp>20080506.124327</timestamp>
</snapshot>
<lastUpdated>20080521165520</lastUpdated>
</versioning>
</metadata>
What´s going wrong here? Why do I always get the LATEST-1 SNAPSHOT, not
the last?
Thanx for any advice,
torsten
Antwort: Latest deployed SNAPSHOT version not downloaded
Posted by to...@gi-de.com.
solution is bottom posted
torsten.reinhard@gi-de.com
26.05.2008 11:56
Bitte antworten an
users@archiva.apache.org
An
archiva-users@maven.apache.org
Kopie
Thema
Latest deployed SNAPSHOT version not downloaded
Hi,
I use Maven 2.0.9 and Archiva 1.0.2, Archiva manages my own "internal" and
"snapshot" company repo.
Since a couple of days, I have problems with downloading SNAPSHOT versions
from my Archiva Managed Repo.
Archiva (or Maven?) is not downloading the latest version, the download
takes the previous version before the latest SNAPSHOT (Latest minus 1).
In the Repo I can see
D:\Archiva\repositories\snapshots\com\gide\logging\gide-revision-logging\3.1.0-SNAPSHOT
gide-revision-logging-3.1.0-20080421.164814-1.jar
gide-revision-logging-3.1.0-20080421.171134-2.jar
gide-revision-logging-3.1.0-20080422.131203-3.jar
gide-revision-logging-3.1.0-20080506.124327-4.jar
gide-revision-logging-3.1.0-SNAPSHOT.jar
When I do a local build, the dependency is resolved to
gide-revision-logging-3.1.0-20080506.124327-4.jar and
gide-revision-logging-3.1.0-SNAPSHOT.jar
in my \localrepo, being gide-revision-logging-3.1.0-SNAPSHOT.jar the same
as gide-revision-logging-3.1.0-20080506.124327-4.jar
the "maven-metadata.xml" is like:
<?xml version="1.0" encoding="UTF-8"?>
<metadata>
<groupId>com.gide.logging</groupId>
<artifactId>gide-revision-logging</artifactId>
<version>3.1.0-SNAPSHOT</version>
<versioning>
<snapshot>
<buildNumber>4</buildNumber>
<timestamp>20080506.124327</timestamp>
</snapshot>
<lastUpdated>20080521165520</lastUpdated>
</versioning>
</metadata>
What´s going wrong here? Why do I always get the LATEST-1 SNAPSHOT, not
the last?
Thanx for any advice,
torsten
=> the problem was in my <distributionManagement> section of a parent
pom.xml
uniqueVersion was set to "false" instead of "true".
<snapshotRepository>
<id>snapshots</id>
<uniqueVersion>true</uniqueVersion>
<name>Archiva Managed Snapshot repository</name>
<url>dav:${repositories.root}/snapshots/</url>
</snapshotRepository>
Torsten
Antwort: Latest deployed SNAPSHOT version not downloaded
Posted by to...@gi-de.com.
solution is bottom posted
torsten.reinhard@gi-de.com
26.05.2008 11:56
Bitte antworten an
users@archiva.apache.org
An
archiva-users@maven.apache.org
Kopie
Thema
Latest deployed SNAPSHOT version not downloaded
Hi,
I use Maven 2.0.9 and Archiva 1.0.2, Archiva manages my own "internal" and
"snapshot" company repo.
Since a couple of days, I have problems with downloading SNAPSHOT versions
from my Archiva Managed Repo.
Archiva (or Maven?) is not downloading the latest version, the download
takes the previous version before the latest SNAPSHOT (Latest minus 1).
In the Repo I can see
D:\Archiva\repositories\snapshots\com\gide\logging\gide-revision-logging\3.1.0-SNAPSHOT
gide-revision-logging-3.1.0-20080421.164814-1.jar
gide-revision-logging-3.1.0-20080421.171134-2.jar
gide-revision-logging-3.1.0-20080422.131203-3.jar
gide-revision-logging-3.1.0-20080506.124327-4.jar
gide-revision-logging-3.1.0-SNAPSHOT.jar
When I do a local build, the dependency is resolved to
gide-revision-logging-3.1.0-20080506.124327-4.jar and
gide-revision-logging-3.1.0-SNAPSHOT.jar
in my \localrepo, being gide-revision-logging-3.1.0-SNAPSHOT.jar the same
as gide-revision-logging-3.1.0-20080506.124327-4.jar
the "maven-metadata.xml" is like:
<?xml version="1.0" encoding="UTF-8"?>
<metadata>
<groupId>com.gide.logging</groupId>
<artifactId>gide-revision-logging</artifactId>
<version>3.1.0-SNAPSHOT</version>
<versioning>
<snapshot>
<buildNumber>4</buildNumber>
<timestamp>20080506.124327</timestamp>
</snapshot>
<lastUpdated>20080521165520</lastUpdated>
</versioning>
</metadata>
What´s going wrong here? Why do I always get the LATEST-1 SNAPSHOT, not
the last?
Thanx for any advice,
torsten
=> the problem was in my <distributionManagement> section of a parent
pom.xml
uniqueVersion was set to "false" instead of "true".
<snapshotRepository>
<id>snapshots</id>
<uniqueVersion>true</uniqueVersion>
<name>Archiva Managed Snapshot repository</name>
<url>dav:${repositories.root}/snapshots/</url>
</snapshotRepository>
Torsten