Overview
This project uses Subversion to manage its source code. Instructions on Subversion use can be found at http://svnbook.red-bean.com/.
Anonymous Access
The source can be checked out anonymously from Subversion with this command:
$ svn checkout http://svn.apache.org/repos/asf/maven/doxia/doxia-sitetools/tags/doxia-sitetools-1.7.2/doxia-integration-tools doxia-integration-tools
Developer Access
Everyone can access the Subversion repository via HTTP, but committers must checkout the Subversion repository via HTTPS.
$ svn checkout https://svn.apache.org/repos/asf/maven/doxia/doxia-sitetools/tags/doxia-sitetools-1.7.2/doxia-integration-tools doxia-integration-tools
To commit changes to the repository, execute the following command to commit your changes (svn will prompt you for your password):
$ svn commit --username your-username -m "A message"
Access from Behind a Firewall
For those users who are stuck behind a corporate firewall which is blocking HTTP access to the Subversion repository, you can try to access it via the developer connection:
$ svn checkout https://svn.apache.org/repos/asf/maven/doxia/doxia-sitetools/tags/doxia-sitetools-1.7.2/doxia-integration-tools doxia-integration-tools
Access Through a Proxy
The Subversion client can go through a proxy, if you configure it to do so. First, edit your "servers" configuration file to indicate which proxy to use. The file's location depends on your operating system. On Linux or Unix it is located in the directory "~/.subversion". On Windows it is in "%APPDATA%\Subversion". (Try "echo %APPDATA%", note this is a hidden directory.)
There are comments in the file explaining what to do. If you don't have that file, get the latest Subversion client and run any command; this will cause the configuration directory and template files to be created.
Example: Edit the 'servers' file and add something like:
[global] http-proxy-host = your.proxy.name http-proxy-port = 3128