[jira] Reopened: (MAVENPROXY-13) SNAPSHOT artifacts are cached

[ji...@codehaus.org]

Message:

   The following issue has been reopened.

   Reopener: Ben Walding
       Date: Fri, 17 Sep 2004 8:58 PM

Damn I thought I'd get away with closing it ;)

Will take a look at it soon.  Overhauling big chunks of it.
---------------------------------------------------------------------
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: Fri, 17 Sep 2004 8:58 PM

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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org