Regarding this problem "network proxy fails after upgrading to archiva 1.1" (http://jira.codehaus.org/browse/MRM-884); I am new to Archiva, and just finished getting 1.0.2 running. I decided to convert to 1.1 before going live, but have hit this problem. My Archiva repositories are currently empty. If my plan is to point maven to an Archiva internal repository, and proxy to the central repository, and control what is downloaded from the central repository with white-lists, does this mean I cannot use 1.1? Are my options to roll back to 1.0.2, or to go directly to the central repository (bypass Archiva), then to upload all these items into my internal repository from my local repository, so that Archiva does not have to download anything? (I hope that makes sense).
This may seem obvious, but I'm still trying to understand the maven/archiva, internal/external/proxy repository relationship. I may have gone as far as I can do without either changing my methodology or my version. Thanks, Mark On Wed, 23 Jul 2008 09:36:04 GMT, djeanprost <[EMAIL PROTECTED]> wrote > I raised a bug. http://jira.codehaus.org/browse/MRM-884. Wait and see. > >
