You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by ji...@codehaus.org on 2004/09/15 16:51:12 UTC
[jira] Commented: (MAVENPROXY-13) SNAPSHOT artifacts are cached
The following comment has been added to this issue:
Author: Joerg Schaible
Created: Wed, 15 Sep 2004 10:51 AM
Body:
Just detected in the log of maven-proxy, that the reason for not downloading a newer SNAPSHOT might be causewd by following log entry. The date is the date of the file in the proxy's cache on the local file system. Any idea how to circumvent the problem?
======= %< ========
16:23:07.355 WARN!! Exception for /picocontainer/jars/picocontainer-1.1-SNAPSHOT.jar
java.lang.IllegalArgumentException: Cannot convert date: Fr, 03-Sep-04 09:57:14
at org.mortbay.http.HttpFields.getDateField(HttpFields.java:916)
at org.mortbay.http.HttpMessage.getDateField(HttpMessage.java:457)
at org.mortbay.jetty.servlet.ServletHttpRequest.getDateHeader(ServletHttpRequest.java:275)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:742)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:360)
at org.mortbay.jetty.servlet.ServletHandler.dispatch(ServletHandler.java:651)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:558)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1714)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1664)
at org.mortbay.http.HttpServer.service(HttpServer.java:863)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:775)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:939)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:792)
at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:201)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:289)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:455)
108732 [PoolThread-0] INFO maven.proxy.RepositoryServlet - Received request: /picocontainer/jars/picocontainer-1.1-SNAPSHOT.jar.md5
139477 [PoolThread-0] WARN maven.proxy.RepositoryServlet - Could not find upstream resource :/picocontainer/jars/picocontainer-1.1-SNAPSHOT.jar.md5
======= %< ========
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MAVENPROXY-13?page=comments#action_24112
---------------------------------------------------------------------
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: Open
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: Wed, 15 Sep 2004 10:51 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org