- 1 How to download the Open-Xchange Server source code (6.22.0 and later)
- 2 How to download the Open-Xchange Server source code (6.20.7 and earlier)
How to download the Open-Xchange Server source code (6.22.0 and later)
Starting with 6.22 the source code of Open-Xchange server is available from our git repository.
The following repositories exist:
|wd/backend||the main repository containing most of the parts of Open-Xchange server|
|frontend6||The AJAX user interface|
GIT operations to access the code
To clone a repository, run
$ git clone http://code.open-xchange.com/git/<repository>
Our release branches are named
release-<releasenumber>, so to access e.g. the release branch for the 6.22.1 release, use
$ cd <repository> $ git checkout -t origin/release-6.22.1
How to download the Open-Xchange Server source code (6.20.7 and earlier)
The source code of Open-Xchange Server is available using cvs access and source packages. Please make sure to use an up-to-date CVS client (cvs > 1.12) to check out the repositories. Integrated CVS clients e.g. for current Eclipse version work well, too.
The currently maintained cvs repositories
|open-xchange||the main repository containing most of the parts of Open-Xchange server|
|open-xchange-gui||The AJAX user interface|
|open-xchange-admin||the Open-Xchange admin daemon used for provisioning (user creation, etc.)|
|open-xchange-admin-plugin-hosting||contains the commandline tools and the oxinstaller|
CVS operations to access the code
To see a complete list of Open-Xchange cvs repositories, run the following command:
$ cvs -d :pserver:firstname.lastname@example.org:/cvsroot rls
Note, however, that only the repositories as listed above are actively maintained.
To check out a repository, run
$ cvs -d :pserver:email@example.com:/cvsroot co open-xchange/com.openexchange.authentication.ldap
to check out the ldap authentication plugin.
Organization of the open-xchange repository
The open-xchange repository contains several OSGi bundles which are the building block of the Open-Xchange server package. Each of them has an ant build.xml file containing a target to create a source tarball and a subdirectory called packaging which contains the package metadata to build DEB and RPM packages.