Source Repositories

Source Repository Structure

The Subversion source repository is structured as different modules, each with its independent main trunk, branches and tags, as it enables us to have independent release cycles for these modules.

The top-level modules are:

• java/
• dotnet/
• ruby/
• php/
• book/
• site/

The platform modules are further subdivided into separate modules for Pico/Nano/MicroContainer (where available). Additional sub-modules per platform can be present, eg for Java NanoContainer, where the module is sufficiently scoped to require its own release cycle.

Browse repository

The repository can be browsed at http://svn.picocontainer.codehaus.org/

Java modules

The Java module paths are

• java/picocontainer/
• java/nanocontainer/
• java/nanocontainer-ioc/
• java/nanocontainer-nanowar/
• java/nanocontainer-persistence/
• java/nanocontainer-remoting/
• java/nanocontainer-sandbox/
• java/nanocontainer-tools/
• java/microcontainer/
• java/demos/

.Net modules

The .Net module paths are

• dotnet/picocontainer/
• dotnet/nanocontainer/

Ruby modules

The Ruby module paths

• ruby/picocontainer/

Php modules

The Php module paths

• php/picocontainer/

Http Access

In the following, <module-path> is one of the paths listed above (eg java/picocontainer) and <module-name> is the name of the checked out module in your local working copy.

Anonymous Access

svn co http://svn.codehaus.org/picocontainer/<module-path>/trunk <module-name>

Example: to check out the Java implementation of PicoContainer (The container only)

svn co http://svn.codehaus.org/picocontainer/java/picocontainer/trunk container

Tip If you are having troubles getting the URL right, you can open your web browser to http://svn.codehaus.org/picocontainer and manually browse through the tree until you get module you are looking for.

Developer Access over SSH

Since CodeHaus has migrated to new servers, Developer Access over SSH has been disabled.  Use secure WebDAV access instead. (See below)

WebDav Access

WebDav is an alternative access protocol supported by SVN and being http-based is often allowed by corporate firewalls.

WebDAV over SSL:

svn co https://svn.codehaus.org/picocontainer/<module-path>/trunk

This access protocol is available to all, but only developers can commit changes. Developers require a unix password for Codehaus username (contact Bob at the Haus to get assigned a password if you don't have one).

To test https commit access, one may eg:

svn co https://svn.codehaus.org/picocontainer/java/picocontainer/trunk picocontainer
cd picocontainer
echo "test" > TEST
svn add TEST
svn commit --username username --password your-password --message "Testing https"

Note: you only need to specify username and password once per client.

svn cp/mv: currently not possible via WebDav, due to the configuration of httpd proxy. If you need to do any svn cp or mv you will have to use svn+ssh access, until the Haus httpd is upgraded (very soon).