On Mon, Feb 23, 2009 at 9:25 AM, <[email protected]> wrote: > The point is that in the archiva webapp the browse page is empty. Meaning > that the repositories are never scanned. Meaning that something with the > network is wrong, but not the proxy config as it works without archiva. Got > it ?
You haven't mentioned putting anything in the repositories, so I expect them to be empty. Just setting up a proxy connector won't do it... you can't browse through to the entire contents of the proxied repos, you will only see the contents of your managed repos, once artifacts have been deployed or proxied. Try constructing a url to an artifact you know is in the remote repo but not in your managed repo, such as: http://[server:port]/archiva/repository/[repoid]/org/apache/struts/struts2-core/2.1.6/struts2-core-2.1.6.jar Does that work in a browser or with wget? (Note that this url is straight to the managed repo, it does not have /browse/ in it.) -- Wendy
