I tried replacing the wagon provider api jar. Still get
Failures occurred downloading from some remote repositories Download failure on resource [xxxxxxxxxxxxxxxxxxxxxxxxxxx]:Error transferring file Thanks Jeff -----Original Message----- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: 28 July 2008 14:14 To: [email protected] Subject: Re: Upgrade from 1.0 to 1.1 : network problem The source code is here: http://svn.apache.org/repos/asf/archiva/trunk/ I believe it is also sufficient to replace the wagon-provider-api JAR in the 1.1 webapp with: http://people.apache.org/~brett/staged-releases-wagon/org/apache/maven/w agon/wagon-provider-api/1.0-beta-4/wagon-provider-api-1.0-beta-4.jar Cheers, Brett 2008/7/28 Dan Dare <[EMAIL PROTECTED]>: > > If the problem has been fixed (indicated in JIRA) how do I get hold of the > changes that were necessary for the fix ? Source code or SNAP-SHOT is fine > > > Brett Porter wrote: >> >> If you need a network proxy to access central from your repository >> server, unfortunately you'll need to use 1.0.2 or wait for a fix to >> the issue below (which we're working on this weekend). >> >> Cheers, >> Brett >> >> 2008/7/26 Mark Johnson <[EMAIL PROTECTED]>: >>> 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. >>>> >>>> >>> >> >> >> >> -- >> Brett Porter >> Blog: http://blogs.exist.com/bporter/ >> >> > > -- > View this message in context: http://www.nabble.com/Upgrade-from-1.0-to-1.1-%3A-network-problem-tp1858 7462p18688926.html > Sent from the archiva-users mailing list archive at Nabble.com. > > -- Brett Porter Blog: http://blogs.exist.com/bporter/ To read FirstRand Bank's Disclaimer for this email click on the following address or copy into your Internet browser: https://www.fnb.co.za/disclaimer.html If you are unable to access the Disclaimer, send a blank e-mail to [EMAIL PROTECTED] and we will send you a copy of the Disclaimer.
