Still no good. I just tried using all combinations of the archiva/proxy URL including archiva/proxy/repo_id, archiva/proxy/repo_id/repo-url-suffix, archiva/proxy/repo-url-suffix all of them with and without a URL suffix assigned to the repo instance. Is there any work being done to make this less painful? I almost feel like digging into the source myself if I didn't already have a dozen other overly complicated projects going on.
Michael Horwitz wrote: > > The snippet offereded is wrong (at least as I remember it). I don't have > access to my archiva install at the moment, but the url must be of the > form > /archiva/proxy/repo_id where repo_id is the id you assigned to your > managed > repository. > > Mike. > > On 12/20/06, Cliff <[EMAIL PROTECTED]> wrote: >> >> >> I use the one provided through archiva itself under managed repositories >> -> >> POM snippet drop-down. I paste that into my settings.xml as my default >> profile and also in my POM and Maven constructs the final URL when it >> attempts to access archiva. I copy that URL from the cmd console and >> paste >> it into my browser to doulbe check and indeed it fails. I also try >> browsing >> archiva the normal way with my browser and pulling up the resource using >> the >> search dialog. After I navigate to the resouce in question clicking the >> download button throws another 404. The base URL is: >> http://shared-server.com:port/archiva/repository/ >> where shared-server and port is the actual server DNS names and bound >> port >> number. (It's not a DNS issue otherwise I would not be able to access >> archiva at all from my browser using the DNS name. Also raw IP gives the >> same results.) >> >> >> Michael Horwitz wrote: >> > >> > Hi, >> > >> > What URL are you using to access your repository? >> > >> > On 12/19/06, Cliff <[EMAIL PROTECTED]> wrote: >> >> >> >> >> >> Help! >> >> >> >> I'm trying to replace Maven-proxy with Archiva but I'm not having much >> >> luck. >> >> I thought I set everything up correctly since I'm able to perform >> >> searches >> >> on our local artifacts but for some reason whenever I try to download >> >> something from archiva I get 404 errors. It looks like archiva is >> finding >> >> the artifact for our project in its local folder but then looking for >> >> them >> >> on the ibiblio proxy repo that I configured. I tried removing the >> proxy >> >> from >> >> the configuration but I still get the 404 errors. Could somebody help >> me? >> >> -- >> >> View this message in context: >> >> http://www.nabble.com/Archiva-almost-works-tf2848067.html#a7953999 >> >> Sent from the archiva-users mailing list archive at Nabble.com. >> >> >> >> >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/Archiva-almost-works-tf2848067.html#a7990390 >> Sent from the archiva-users mailing list archive at Nabble.com. >> >> > > -- View this message in context: http://www.nabble.com/Archiva-almost-works-tf2848067.html#a7991918 Sent from the archiva-users mailing list archive at Nabble.com.
