Moved to Subversion

Cocoon CVS repositories are moved into the Apache Subversion Repository. This page is meant to collect information about this move, and help people configure their SVN clients.

Committers warning

By default, svn client saves the credentials in your hardisk in plain text in ~/.subversion/auth/svn.simple/*.

If you want to disable the credential caching permanently, edit the runtime config file (in *NIX ~/.subversion/config) and add:

store-auth-creds = no

Repository Details

See also

There were two active CVS respositories, cocoon-2.1 and cocoon-2.2. Former had two branches, BRANCH_2_1_X and HEAD. Latter has only HEAD.

cocoon-2.1's BRANCH_2_1_X was started out of RELEASE_2_1_5 tag, and has one release, tagged as RELEASE_2_1_5_1. cocoon-2.1's HEAD contains code of cocoon-2.2-dev, next minor version of Cocoon.

cocoon-2.2's HEAD, despite its name, actually contains experimental code for the new Cocoon kernel which might grow into the foundation of Cocoon's "real blocks".

When CVS repositories were migrated into the Subversion, naming confusion was resolved, by clearly marking what is where. Thus,

Practice SVN repository

The practice repository found at can be used to test your SVN client. This URL is read-only.

For committers, a writable test repository is available at To generate a password, ssh to and run the following command:

svnpasswd username

This will ask you for a subversion password. This is the user and password you can use when checking in code.

To switch from the http to the https repository use

svn sw --relocate

Subversion clients

(please list your favorite clients here)

Quirks with some clients

If you get: "unknown url scheme" then recompile your svn client with ssl support. On linux use

./configure --with-ssl

Use recent version of Subclipse

The latest versions of Subclipse are hidden in the depth of the menus at their website. At find the latest builds.



Find the latest Subclipse plugin at In order to install it, choose [Help - Software Updates - Install/Update] and then "Search for new features to install" and "Add Update Site". Enter "" there. (Tested with with Eclipse 3.0 -- ReinhardPoetz)

Subclipse HTTPS support

Currently the certificate for is self-signed. Subclipse doesn't offer a possibility to accept it. A workaround is using the command-line client of SVN and accept the untrusted certifcate permanently at your first connection, then Subclipse will be happy.

Subversion resources

SubversionMigration (last edited 2009-09-20 23:40:31 by localhost)