SourceCodeAccess: Difference between revisions

From Open-Xchange
No edit summary
No edit summary
Line 1: Line 1:
= How to access the Open-Xchange Server source code =
= How to access the Open-Xchange Server source code =


The source code is currently only available using cvs access.
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 ==
== The currently maintained cvs repositories ==

Revision as of 00:49, 14 August 2010

How to access the Open-Xchange Server source code

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

Repository content
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
open-xchange-admin-soap SOAP interface

CVS operations to access the code

To see a complete list of Open-Xchange cvs repositories, run the following command:

$ cvs -d :pserver:anonymous@www.open-xchange.com:/cvsroot rls

Note, however, that only the repositories as listed above are actively maintained.

To check out a repository, run

$ cvs -d :pserver:anonymous@www.open-xchange.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.