Skip to Content

Wiki source code of Repository Access

Version 1.1 by 5fbc055b7cc103006957e1ae on 2012-06-15 12.17:54
Hide last authors
5fbc055b7cc103006957e1ae 1.1 1 (% style="" %)
2 === {{id name="RepositoryAccess-Publicaccess"/}}Public access ===
3
4 The Clazzes.org subversion and maven repositories can be accessed read-only by anonymous users. The URLs all follow the same schema, just replace {{code language="none"}}project-name{{/code}}. Generally, the svn and maven urls for all projects should also be written on their homepage. If you are not sure about the project name, you can visit [[https:~~/~~/maven.clazzes.org/org/clazzes/>>url:https://maven.clazzes.org/org/clazzes/||style="" shape="rect"]] and browse the list of projects there, or contact the project lead.
5
6 (% style="" %)
7 * Subversion: http:~/~/svn.clazzes.org/svn/project-name/
8 * Maven Releases: http:~/~/maven.clazzes.org/org/clazzes/project-name
9 * Maven Snapshot-Releases: (% class="nolink" %)http:~/~/maven-snapshots.clazzes.org/org/clazzes/project-name
10
11 (% style="" %)
12 === {{id name="RepositoryAccess-Authenticatedaccess"/}}Authenticated access ===
13
14 (% style="" %)
15 Every project has a designated user name (usually the same as the project name), which may upload files subversion and maven repositories via ssh. Trusted user's ssh-keys are added to the authorized key list of the project-user. Access may be restricted to svn or include and the maven repository.
16
17 (% style="" %)
18 Write-enabled URLs for projects are built according to the following schema:
19
20 (% style="" %)
21 * Subversion repository: svn+ssh:~/~/project-name@svn.clazzes.org/svn/project-name
22 * Maven repository base URL: scpexe:~/~/project-name@maven.clazzes.org/var/www/htdocs/maven.clazzes.org
23 * Maven snapshot repository base URL: scpexe:~/~/project-name@maven.clazzes.org/var/www/htdocs/maven-snapshots.clazzes.org
24 * In place of {{code language="none"}}scpexe:{{/code}} you may be able to use {{code language="none"}}sftp:{{/code}} or {{code language="none"}}scp:{{/code}}
25
26 (% style="" %)
27 ==== {{id name="RepositoryAccess-Troubleshootingauthenticatedaccess"/}}Troubleshooting authenticated access ====
28
29 (% style="" %)
30 Before contacting the administrator or project lead because of technical problems, please make sure you have tried the following:
31
32 (% style="" %)
33 * Your ssh client must accept the clazzes.org server’s host keys before you can commit using {{code language="none"}}ssh+svn{{/code}}. In a terminal, call 
34 {{code language="none"}}ssh svn.clazzes.org{{/code}} and {{code language="none"}}ssh maven.clazzes.org{{/code}} once and accept the host key.
35 * If you have already made changes in a working copy downloaded via public access you can switch it to ssh-based access without loosing anything: svn switch ~-~-relocate (% class="nolink" %)http:~/~/svn.clazzes.org/project-name(%%) svn+ssh:~/~/util@svn.clazzes.org/svn/project-name
36 * Some maven plugins do not understand the {{code language="none"}}user@{{/code}} part of scp/scpexe/sftp URLs nor the user setting in ~~/.m2/settings.xml or ~~/.ssh/config, you will need to call the maven CLI tool with an option like -Duser.name=project-name. Like: maven -Duser.name=project-name deploy
37 * If extending or creating a {{code language="none"}}pom.xml{{/code}}, do not forget that at some points you need to use complete URLs, i.e. append {{code language="none"}}/trunk/project-name{{/code}} or the like.