
Make sure that you downloaded the OLAT source code and read the installation documentation before you start developing for OLAT.
For bug tracking and enhancement issues we use JIRA. Go to bugs.olat.org to see which bugs are open or already fixed and which features are in the development process. If you find a new bug please do post that bug on our developers' mailing list. If we can reproduce the bug we will add it to the bug tracking system. Please do always search for existing bug reports before you send a mail. To watch what is committed and by whom visit our fisheye CVS view:
The technical documentation explains the installation process and gives you hints on how to customize your OLAT installation. This documentation is only available in English and updated frequently. The single-page version is identical to the multiple-pages version but rendered as one big HTML page for better searching and printing. Many thanks to all those developers who contributed to OLAT's technical documentation! Special thanks go to the MELS development team who wrote most of the documentation. More technical manuals and information can be found in the Development section.
The technical documentation chapter covers OLAT concepts, system architecture and the OLAT development framework.
OLAT 6 and the underlying brasato framework have a totally new layout concept based on the YAML framework. Using YAML and the new brasato framework OLAT 6 will offer a lot of improvements towards clean, browser-independent and accessible layout. Please have a look at the following technical documentation if you plan to adapt the OLAT layout to your needs.
This documentation by Florian Gnägi explains how translation and internationalization work in OLAT. It also contains extensive information about the new translation tool.
If you would like to develop some extensions or just play with the source code and debug some workflows of a running OLAT you will need to run OLAT out of the Eclipse IDE. Check our installation documentation plus there is a nice guide available from BPS about setting up an OLAT development environment under the Eclipse IDE. We suggest to use the Eclipse WTP build which includes by default a lot of useful plugins
The generated javadoc of the source code can be found here. A good starting point is the top level package org.olat which contains a graphical overview. You will find technical explanations of packages and code examples.
We use the
Concurrent Versioning System (CVS) to manage the OLAT source code. If you are interested in the cutting-edge version of OLAT or if you want to develop OLAT
extensions you should check the OLAT CVS HEAD. We recommend checking OLAT from within the Eclipse IDE (see above). We develop
using Eclipse; all project settings are also part of the project.
When checking OLAT on a shell use the following commands:
If you want to send us some code, please send only patches you have made using the patch mechanism from Eclipse. Send us the patch via the developers' mailing list.
See the fisheye cvs archive viewer to get an impression of current development activities.
This document explains how the OLAT Test Environment using Selenium works at the University of Zurich. This document is not of general interest for non-UZH developers.
At the University of Leipzig Prof. Gräbe is using OLAT in his Knowledge Environment Engineering Seminar. Students have done some quite interesting research papers about OLAT there: