Ode uses Subversion to manage its source code. Instructions on Subversion use can be found here.

Main repository

Web Access


Anonymous access

Ode source can be checked out anonymously with this command:

Once you have Ode checked out you can update the source by executing the following command from within the ode directory.

Once you've got the code you'll probably want to build it; for instructions see [Building Building].

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 HTTPS:

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 files 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 :

Submitting a Patch

If you make changes to Ode, and would like to contribute the to the project, you should create a patch and post it to the [issues.apache.org/jira/browse/ODE Ode JIRA issue tracker]. To create a patch, simply execute the following command:

Developer Access

Everyone can access the Ode Subversion repository via HTTPS, but Ode Committers must checkout the Subversion repository via HTTPS.

To commit changes to the repository, you must set your password on the Apache Subversion server. To set your password, use ssh to connect to svn.apache.org, and enter the command svnpasswd. This will prompt you to enter a svn password of your choice (pick a safe password). Now, now your are ready to commit changes using your username/password. Execute the following command to commit your changes (svn will prompt you for your password)

You can also pass your password on the command line directly, but this is a security problem on multiuser unix computers (the command line arguments are available via the ps command). Here is the command if you are Windows or a single user unix computer:

Remember to replace 'your-username' and 'your-password' with your actual username and password on svn.apache.org.

Subversion client config

Add this to your subversion client configuration file:

Note: make sure the settings are merged into the appropriate section if it already exists, as duplicate section names can cause problems.

Possible locations of your subversion client configuration

Note: The names of svn keywords that are substituted in files may not match the SVN keywords in this config file. This is because a number of SVN keywords have alternate names that can be used. For example the "Revision" keyword may be specified as "Rev" and "LastChangedRevision" and can be used interchangably. This file uses the standard Subversion Keywords, not their alternate forms for clarity and consistency with the Subversion config files used by other ASF projects. This config file does not need to be changed to use the alternate forms for the alternate forms to be able to be used. For further information on Subversion keywords see http://svnbook.red-bean.com/en/1.1/ch07s02.html#svn-ch-7-sect-2.3.4.

To verify the auto-props processing is working you can test adding a file without committing it (Windows example):

If you didn't get the results above, double check that the following line in the [miscellany] section is set and not commented out or set elsewhere.

GettingSourceCode (last edited 2009-09-20 23:19:40 by localhost)