archiva-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zemian Deng" <keepitsimpl...@gmail.com>
Subject Re: daisy chain archiva webapp proxies doesn't seem to work
Date Thu, 21 Aug 2008 04:18:11 GMT
Hello Brett,

I am pretty sure the connector are right because I can get the previous
version of the artifact, just not the one I released today.

I will double check again in the morning and let you know.

Thanks,
-Z

On Wed, Aug 20, 2008 at 8:36 PM, Brett Porter <brett.porter@gmail.com>wrote:

> 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 <keepitsimple12@gmail.com>:
> > 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:
> > http://code.google.com/p/sweetscala
> >
>
>
>
> --
> Brett Porter
> Blog: http://blogs.exist.com/bporter/
>



-- 
Sweet - a Scala web framework:
http://code.google.com/p/sweetscala

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message