Name:
Password:
remember me
or register
Valid XHTML 1.0 Transitional Valid CSS! SourceForge.net Logo
Building Corinis Modules from Subversion
This document shows you how to build the corinis modules using subversion.
Preparation/Software

In order to build corinis you need the required libraries first, see the installation documentation. For the developer environment copy all required classes in the tomcat/common/lib directory. This is where the ant scripts will look for the libraries.

You also need a subversion client. This document uses the commanline client from http://subversion.tigris.org/

Make sure you have apache ant installed (from http://ant.apache.org/ )

Getting the source

First create a directoy where you want to check out the corinis modules to. (Use something like c:corinis or ~/corinis)

Now open a command shell/terminal and change into this directory. Nex check out all the modules you want from svn (remember to check out the Core module since its a dependency for all other modules) using:

mkdir Core
svn co http://svn.corinis.org/svn/Core/trunk/ Core

This creates a new directory named Core and puts the Core module from the svn repository into this one. Repeat this for the other modules you want:

mkdir Cms
svn co http://svn.corinis.org/svn/Cms/trunk/ Cms
mkdir Forum
svn co http://svn.corinis.org/svn/Forum/trunk/ Forum
mkdir Guestbook
svn co http://svn.corinis.org/svn/Guestbook/trunk/ Guestbook
mkdir PhotoLibrary
svn co http://svn.corinis.org/svn/PhotoLibrary/trunk/ PhotoLibrary
mkdir Voting
svn co http://svn.corinis.org/svn/Voting/trunk/ Voting

You will now have the sources of all modules on your harddrive.

Compiling

before compiling create a file named tomcatpath.properties and put following line into it:

tomcatpath=/path/to/tomcat/common/lib/

Make sure to insert correct path to your tomcat/... installation's common/lib directory (where you put the required classes to).

Also make sure you create an "out" directory in the same level as your modules. 

You can now build the modules by entering in each module directory and running ant:

cd Core
ant

 

You will then find the compiled jars and zips in the out directory.

The source directory structure

Here is how a typical directory structure looks like and what you will find into the directories:

~/corinis/
~/corinis/ModuleName/src - the java sources
~/corinis/ModuleName/webroot - the jsp files for each module (administration)
~/corinis/ModuleName/xsl - the admin xsl files for each module
~/corinis/ModuleName/documentation - stuff like license txt or other information
~/corinis/Core - the core module
~/corinis/Core/documentation/corinis.xml - an example corinis.xml (put this in your webroot/WEB-INF)
~/corinis/Core/documentation/corinis.tld - the taglib description file (put this in your webroot/WEB-INF)
~/corinis/tomcatpath.properties - the properties file for the ant scripts
~/corinis/out - the folder where the final jars/zip reside