Our sourcecode is being managed within a subversion-repository (svn).

Developers who are using Kajona in their projects are able to access the latest stage of development besides the regular releases with a public SVN account.

Using any Subversion client like the explorer extension TortoiseSVN for Windows, Kdesvn for Linux or the Eclipse plugin Subclipse, the latest features and changes can be tracked, tested and if applicable integrated into your project prior the next release.

Furthermore the SVN access can ease and improve the update process of a Kajona system in complex projects, because every change of code and files can be followed in detail.

However, more unexperienced developers should still use the ready-to-go release packages in our download section.

SVN repository of all releases
https://svn.kajona.de/svn/kajona/kajona/module_head/tags/

SVN repository of the latest stage of development
https://svn.kajona.de/svn/kajona/kajona/module_head/trunk/
Note: Since this version maybe untestest or not runnable, we strongly advice you not to use this version in production-environments!

SVN repository of tests & playground
https://svn.kajona.de/svn/kajona/kajona/module_head/playground/
Modules and page elements being in an early state of development are located in the playground-repository. Since those elements are of an early age, the quality may not fit the standard of the trunk. In most cases, those entries are being included into the trunk via svn-externals. If you checkout the trunk, those elements should be included in your local working-copy, too.

The login for all repositorys is guest/guest.

Active developers should ask for own logins with write permissions.

The SVN server is provided to us by LCube-Webhosting and Subversion Hosting - thanks a lot!