Hi, Here are 2 questions about Maven Internal Repositories implementation, and protocols that can be used. (because of unclear doc - imo - about repositories, wagon, and settings.xml (id/user/pwd) )
statement 1 (before question 1) >From what I've read on wagon's site (http://maven.apache.org/wagon/), it is possible for maven repository access to use: * File (download/upload) * HTTP (download only) * HTTP lightweight (download only) * FTP (download/upload) * SSH/SCP (upload only / download not fully tested) * WebDAV (upload only / download not fully tested) * SCM (in progress) question 1: is this information up to date ? statement 2 (before question 2) Until now, I've used Maven (internal) repositories with file system access (file://) for download and upload. This is no problem... everything works fine :-) Now, I am in the process of implementing our internal repositories on Unix server, and securing these repositories, without using (at this time) any repository manager (archiva, artifactory, ...) I want to use something very very reliable: therefore, giving that we have to put the repositories on unix server and we want to access them from windows and unix maven clients the following solution seems appropriate: => for artifacts download, use an http server => for artifacts upload, use an ftp server (or a webdav server) regarding the repository definitions, our corporate pom should look like: <distributionManagement> <repository> <id>internalDeploy</id> <name> company released artifacts </name> <url>ftp://mvnftpserver/maven2repository</url> </repository> ... <repositories> <repository> <id>internalShared</id> <name> company released artifacts </name> <url><url>http://www.mvn-server.com/maven2repository</url> </repository> ... when it gets to security, the "Security and Deployment Settings" doc (http://maven.apache.org/guides/mini/guide-deployment-security-settings.html) is not really clear: Before its given example, it states: "As of the first release, only SCP deployments and file deployments are supported by default, so only the following SCP configuration is needed: ..." on the other hand, latest Maven book gives an example with ftp. so .. question 2: If both servers need a signon (possibly with different user/password ) will it be ok to have for Maven users the following settings.xml : <server> <id>internalDeploy</id> <username>ftp_user</username> <password>blabla</password> </server> <server> <id>internalShared</id> <username>user_xyz</username> <password>blabla</password> </server> and more generally what is the usage scope of the <server> ... </server> specs in settings.xml ? Thanks for any additionnal info, Christian-Luc -- View this message in context: http://www.nabble.com/Maven-Repositories-acess---servers---signon-specs-in-settings.xml-tf4568000s177.html#a13037401 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
