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/09 21:05:43 UTC
[jira] Created: (MAVENPROXY-13) SNAPSHOT artifacts are cached
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
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: Thu, 9 Sep 2004 5:56 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
[jira] Closed: (MAVENPROXY-13) SNAPSHOT artifacts are cached
Posted by ji...@codehaus.org.
Message:
The following issue has been closed.
Resolver: Ben Walding
Date: Thu, 16 Sep 2004 7:10 AM
Thanks Emmanuel, after thinking a bit more (about the stacktrace) I thought it might be maven pushing in dodgy values.
Closing - ping me if the HttpUtil fixes don't work and I'll look into it more.
---------------------------------------------------------------------
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: Closed
Priority: Critical
Resolution: WON'T FIX
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: Thu, 16 Sep 2004 7:10 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
[jira] Commented: (MAVENPROXY-13) SNAPSHOT artifacts are cached
Posted by ji...@codehaus.org.
The following comment has been added to this issue:
Author: Emmanuel Venisse
Created: Thu, 16 Sep 2004 3:43 AM
Body:
I've patched HttpUtils for encoded all date to english format. So, it must be works correctly if you update your HttpUtils class in maven.
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MAVENPROXY-13?page=comments#action_24139
---------------------------------------------------------------------
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: Thu, 16 Sep 2004 3:43 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
[jira] Commented: (MAVENPROXY-13) SNAPSHOT artifacts are cached
Posted by ji...@codehaus.org.
The following comment has been added to this issue:
Author: Ben Walding
Created: Wed, 15 Sep 2004 5:38 PM
Body:
Are you running under a French language pack or something like that?
It looks like Jetty's language handling might be sub-par. I'll take a better look today hopefully.
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MAVENPROXY-13?page=comments#action_24120
---------------------------------------------------------------------
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 5:38 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
[jira] Reopened: (MAVENPROXY-13) SNAPSHOT artifacts are cached
Posted by 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
[jira] Commented: (MAVENPROXY-13) SNAPSHOT artifacts are cached
Posted by ji...@codehaus.org.
The following comment has been added to this issue:
Author: Ben Walding
Created: Mon, 20 Sep 2004 4:09 AM
Body:
Yep, I'm working on the snapshot downloading now. It's more convoluted that I'd prefer, but there are a lot of logic paths to do it efficiently.
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MAVENPROXY-13?page=comments#action_24268
---------------------------------------------------------------------
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 4:09 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
[jira] Commented: (MAVENPROXY-13) SNAPSHOT artifacts are cached
Posted by ji...@codehaus.org.
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
[jira] Commented: (MAVENPROXY-13) SNAPSHOT artifacts are cached
Posted by ji...@codehaus.org.
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Closed: (MAVENPROXY-13) SNAPSHOT artifacts are cached
Posted by ji...@codehaus.org.
Message:
The following issue has been closed.
Resolver: Ben Walding
Date: Wed, 22 Sep 2004 11:23 PM
Ok this should be fixed now. If this happens again - raise a new issue as everything has changed.
---------------------------------------------------------------------
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: Closed
Priority: Critical
Resolution: FIXED
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, 22 Sep 2004 11:23 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