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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
