Configuring the build environment

HOW-TOs for developers of the library

• How to get started
• How to configure the JDK with security providers
• How to Install Maven
• How to use Eclipse
• How to configure your subversion client
• How to configure JMeter for load testing
• How to release the SOSI library
• Q/A

Subversion

Soucecode, binary artifacts and all dependencies are found in Subversion at:

https://svn.softwareborsen.dk/sosi

You can browse the sourcecode via web at http://svn.softwareborsen.dk/sosi or you can use an external Subversion client for instance:

Product	URL	OS
Tortoise SVN	http://tortoisesvn.tigris.org	Windows XP
Metissian Subversion Command Line	http://metissian.com/projects/macosx/subversion	Mac OS X

You can also use a Subversion client embedded in your favorite development environment, for instance the Eclipse plugin that can be found at http://subclipse.tigris.org/

Directory Structure

The SOSI component Subversion structure is based on wellknown TTB (Trunk, Tags, Branches) structure. Under that the project contains some external tools (tomcat-xxx/, jmeter-xxx/), all packed releases (releases/), the project license (license/), configurationfiles (config/) and last but not least the source code (modules/). The directory structure is as follows:

  * trunk - Head of repository
    * tomcat-xxx - Tool
    * jmeter-xxx - Tool
    * license - Project License
    * config - Tools config files
    * modules - Source code
      * seal - The SOSI component
        * src - Source folder
          * main - Application source 
          * test - Test source  
      * demo - Demo applications
        * idp - Demo Identity Provider
        * client - Demo SOSI web service client
        * provider - Demo SOSI web service provider
      * maven-jmeter-report-plugin - Maven plugin to generate jmeter report
      * ant-plugin - Maven plugin to handle Ant tasks
  * tags - Tags in repository
  * branches - Branches in repository
  * releases - Releases of Seal

Maven Goals

The SOSI component is built with Apache Maven 2 which must be downloaded and installed. See this link for a how-to. The subprojects can be built separately and will automatically build dependencies, and download libraries etc. After installation you can use standard Maven goals for instance:

> mvn install

Builds and installs the project

> mvn clean

Cleans all artifacts etc.

-- ChristianGasser - 18 Oct 2007