archiva-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter" <>
Subject Re: daisy chain archiva webapp proxies doesn't seem to work
Date Thu, 21 Aug 2008 00:36:10 GMT
No, there's no delay. Are you sure you have the proxy connector from A
to B set up correctly?

2008/8/20 Zemian Deng <>:
> Hi,
> I have to archiva instance running on separated hosts A and B. I have added
> a remote repo of archiveB into archivaA, and for most of the time they works
> great. But sometimes when i do a release to archivaB, the archivaA will not
> pull down the artifact. Is there reason for this?
> I can verify that archivaB does indeed worked becuase i have a project build
> sucessful with the latest dependencies on the artifact x, but when I switch
> to archivaA, it will failed that it can't find the artifact.
> So my question is, is there time period that archiva will wait before it
> check remote repo, even when you have a project requesting a artifact that's
> missing from it? If so, is there way I can force it to pull that down into
> archiva?
> Thanks,
> -Z
> --
> Sweet - a Scala web framework:

Brett Porter

View raw message