The following comment has been added to this issue:
Author: Joerg Schaible
Created: Mon, 20 Sep 2004 2:32 AM
Body:
Just to complete the records for this issue:
I've build the maven-1.0 branch from CVS and the exception in the logfile of
maven-proxy has gone, but it still does not download newer SNAPSHOTs. The logfile
contains entries because of the missing POMs:
====== %< ========
150511091 [PoolThread-1] INFO maven.proxy.RepositoryServlet - Received request:
/picocontainer/jars/picocontainer-1.1-SNAPSHOT.jar.md5
150512963 [PoolThread-1] WARN maven.proxy.RepositoryServlet - Could not find
upstream resource :/picocontainer/jars/picocontainer-1.1-SNAPSHOT.jar.md5
150512991 [PoolThread-4] INFO maven.proxy.RepositoryServlet - Received request:
/nanocontainer/jars/nanocontainer-1.0-SNAPSHOT.jar.md5
150515148 [PoolThread-4] WARN maven.proxy.RepositoryServlet - Could not find
upstream resource :/nanocontainer/jars/nanocontainer-1.0-SNAPSHOT.jar.md5
150515184 [PoolThread-0] INFO maven.proxy.RepositoryServlet - Received request:
/nanocontainer/jars/nanocontainer-ejb-1.0-SNAPSHOT.jar.md5
150517174 [PoolThread-0] WARN maven.proxy.RepositoryServlet - Could not find
upstream resource :/nanocontainer/jars/nanocontainer-ejb-1.0-SNAPSHOT.jar.md5
150517200 [PoolThread-4] INFO maven.proxy.RepositoryServlet - Received request:
/nanocontainer/jars/nanocontainer-jmx-1.0-SNAPSHOT.jar.md5
150519234 [PoolThread-4] WARN maven.proxy.RepositoryServlet - Could not find
upstream resource :/nanocontainer/jars/nanocontainer-jmx-1.0-SNAPSHOT.jar.md5
====== %< ========
OK, they are not available, but looking into the cache, the SNAPSHOTs were not updated
with newer available versions:
====== %< ========
/devel/maven/cache > ll *container/jars/*-SNAPSHOT.*
-rw-r--r-- 1 maven maven 72988 Sep 3 11:57
nanocontainer/jars/nanocontainer-1.0-SNAPSHOT.jar
-rw-r--r-- 1 maven maven 4785 Sep 3 11:57
nanocontainer/jars/nanocontainer-ejb-1.0-SNAPSHOT.jar
-rw-r--r-- 1 maven maven 9189 Sep 3 11:57
nanocontainer/jars/nanocontainer-jmx-1.0-SNAPSHOT.jar
-rw-r--r-- 1 maven maven 63846 Sep 3 11:57
picocontainer/jars/picocontainer-1.1-SNAPSHOT.jar
====== %< ========
Regards,
J�rg
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MAVENPROXY-13?page=comments#action_24266
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MAVENPROXY-13
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVENPROXY-13
Summary: SNAPSHOT artifacts are cached
Type: Bug
Status: Reopened
Priority: Critical
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-component-proxy
Assignee: Ben Walding
Reporter: Joerg Schaible
Created: Thu, 9 Sep 2004 5:56 AM
Updated: Mon, 20 Sep 2004 2:32 AM
Description:
Hi Ben,
I've configured the Maven-proxy to use Codehaus' repo, since I want to use the
Pico/Nano-SNAPSHOTS. These are generated by DamageControl after each commit.
Unfortunately the Maven-proxy seems not to look for newer snapshots, because all of
them are of an old date (first time download) in Maven-proxy's cache.
Since this happens silently, it is absolutely not transparent for any user nor the
expected behaviour.
Regards,
J�rg
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
