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
