You can access SVN through straight-up HTTP, though there are dedicated clients (your mileage may vary, depends on how you have SVN setup). Actually I fixed the problem myself. Turns out that my settings.xml file was incorrect; once I fixed this, the simple approach of pointing the id of my <repository> in the POM to the id of my <server> with the username/password worked just fine.
Yes, I should be using Nexus/Artifactory/Archiva, but I am very *constrained* in my choices to a DEV WebSphere 6.1 server (I can't even put up a Tomcat server, *sigh*). I tried the Artifactory war file on it...several bug fixes later (and JIRAs and patches to the project), it still was not working for me. I didn't have the time to try the same with Archiva (maybe sometime in the future if they support WAS). Since I don't really need the proxy functionality--my main goal is to have a repository for internal projects and for third party libs that are not available on public mvn repositories--this solution works fine for me, at least for now. Thanks for the replies, though. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lee Meador Sent: Tuesday, September 16, 2008 3:49 PM To: Maven Users List Subject: Re: Using repository with HTTP basic auth Subversion is a source code repository. Access is through a subversion client or, possibly, WebDAV. (There are web based clients) Maven's repository typically holds poms and jar files though it can hold pretty much any file at all. Access is by Maven itself although the interface is pretty much a straight file/url based system. I think you either have your terminology mixed in how the message is worded or you are trying to do something that is unlikely to work. If you want to put a Maven repository on a server for shared use, you can use a repo manager like Nexus or Archiva. (There are others.) These tools are made for this purpose and you might be able to host them on the same machine as the one where you host Subversion. Read those application's documentation to see what is possible if you are required to use HTTP basic auth. -- Lee On Tue, Sep 16, 2008 at 1:28 PM, Spies, Brennan <[EMAIL PROTECTED]>wrote: > Hi, > > I am trying to set up a "quick and dirty" internal Maven repository on > Subversion. I've successfully deployed a few artifacts to the repository > using svn-wagon (https://wagon-svn.dev.java.net/), but I want to be able > to > make these dependencies available to other developers with a minimum of > fuss. > Unfortunately, our SVN server doesn't allow any read access without > credentials (user/password via HTTP basic auth)--something I can't > control--so I need to use a <repository> that can authenticate with HTTP > basic. > > I've tried a few approaches (referring to a <servers> id from the > <repository>, using the svn-wagon plugin), but nothing has worked. Is there > a > plugin or other approach I can use to do this? > > Thanks, > > Brennan > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- -- Lee Meador Sent from gmail. My real email address is lee AT leemeador.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
