Let me clarify. What I meant by worked was that my build process didn't fail...

As Emmanuel has correctly pointed out SVN does not use the same format for a connection string as CVS. Quoting the SVN red book:

---------------------------------------------------------------------
Repository URLs

Subversion repositories can be accessed through many different methods—on local disk, or through various network protocols. A repository location, however, is always a URL. Table 2-1 describes how different URL schemas map to the available access methods.

Table 2.1. Repository Access URLs
Schema  Access Method
file:///        direct repository access (on local disk)
http:// access via WebDAV protocol to Subversion-aware Apache server
https://        same as http://, but with SSL encryption.
svn://  access via custom protocol to an svnserve server
svn+ssh://      same as svn://, but through an SSH tunnel.

For the most part, Subversion's URLs use the standard syntax, allowing for server names and port numbers to be specified as part of the URL. Remember that the file: access method is valid only for locations on the same server as the client—in fact, in accordance with convention, the server name portion of the URL is required to be either absent or localhost:

$ svn checkout file:///path/to/repos
…
$ svn checkout file://localhost/path/to/repos
…

Also, users of the file: scheme on Windows platforms will need to use an unofficially “standard” syntax for accessing repositories that are on the same machine, but on a different drive than the client's current working drive. Either of the two following URL path syntaxes will work where X is the drive on which the repository resides:

C:\> svn checkout file:///X:/path/to/repos
…
C:\> svn checkout "file:///X|/path/to/repos"
…

In the second syntax, you need to quote the URL so that the vertical bar character is not interpreted as a pipe.

Note that a URL uses ordinary slashes even though the native (non-URL) form of a path on Windows uses backslashes.
---------------------------------------------------------------------


For now, I'm happy with a working website.... :)

Omair

Emmanuel Venisse wrote:

No svn doesn't use cvs connection string style.

----- Original Message ----- From: <[EMAIL PROTECTED]>
To: "Maven Users List" <[EMAIL PROTECTED]>
Sent: Tuesday, May 25, 2004 6:21 PM
Subject: RE: subversion repo connection string: (again I know)



didn't the scm:svn:pserver:[pserver [EMAIL PROTECTED]:/path/to/svn:my-project-name/trunk works ?

Nicolas,





Omair-Inam Abdul-Matin <[EMAIL PROTECTED]>
Envoyé par : news <[EMAIL PROTECTED]>
25/05/2004 18:09
Veuillez répondre à "Maven Users List"


Pour : [EMAIL PROTECTED] cc : Objet : subversion repo connection string: (again I know)


There was a thread regarding Subversion and a proper connection string for it some time ago. I'm still not sure about the form of the final connection string that pleases Maven.

When I try to build my project I get the following error

BUILD FAILED
File...... C:\Documents and
Settings\oiinamul\.maven\plugins\maven-xdoc-plugin-1
.7.1\plugin.jelly
Element... velocity:merge
Line...... 491
Column.... 13
Invocation of method 'getScmType' in  class
org.apache.maven.project.Repository
threw exception class java.lang.IllegalArgumentException : repository
connection
  string contains less than six tokens
Total time: 1 minutes 45 seconds
Finished at: Tue May 25 12:06:25 EDT 2004

Alas... maven still insists on 6 tokens it seems. So if I have the
following, how do I turn it into 6 acceptable tokens:

scm:svn:http://my-server-name/svn/my-project-name/trunk

I've tried
scm:svn:http://my-server-name:svn:project-name/trunk

didn't work...

Omair


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to