Chapter 1. Building JASMINe
Prev   Next

1.1. Software requirements

1.2. Getting the sources

1.2.1. Structure of the repository

The structure is structured as follows:

				trunk/ assembly/ <- build.xml required files
				jasmine-control/ <- Central node module jasmine-doc/
				<- Documentation jasmine-gui/ <- UI jasmine-jade/
				<- JADE Bundles jasmine-probes/ <- Monitoring
				System build.xml

1.2.2. Command line

Svn command line client is used to checkout the sources: 

>$ svn checkout svn://svn.forge.objectweb.org/svnroot/jasmine/jasmine/trunk
jasmine A jasmine/assembly
A jasmine/assembly/jasmine-control
A jasmine/assembly/jasmine-control/ant
A jasmine/assembly/jasmine-control/ant/README A
jasmine/assembly/jasmine-control/ant/build.xml A
jasmine/assembly/jasmine-control/rars A
jasmine/assembly/jasmine-control/rars/autoload ... A
jasmine/jasmine-probes/jython A
jasmine/jasmine-probes/jython/manager.py A
jasmine/jasmine-probes/jasmine-probe-jython.sh A
jasmine/jasmine-probes/.settings A
jasmine/jasmine-probes/.settings/org.eclipse.jdt.core.prefs
A jasmine/build.xml Checked out revision 184.

This will checkout all the JASMINe code base (Control node components, JADE bundles and wrappers, UI) in a folder named jasmine .

1.2.3. Eclipse Subclipse/Subversive

In the SVN Repository Exploring perspective, add a new repository location with the URL svn://svn.forge.objectweb.org/svnroot/jasmine/jasmine/trunk (or with 'svn:ssh' for a developer access).

Checkout the trunk as a new project (not Java project). Then, simply import the projects inside in your workspace.

It's important to keep the Jasmine projects structure, otherwise the JASMINe build process will not work.

[Note]Note

Use the protocol svn+ssh (instead of svn) for developer access. Anonymous users are unable to commit changes.

1.3. Ant process

Prior to the build execution, the following environment variables must be set:

Executing ant in the jasmine/ directory will compile everything and produce the distributable binaries in the output/dist/ directory: 

			>$ ant jar Buildfile: build.xml

			init:

			jar-probes: ... parent: [copy] Copying 1 file to
			/home/sauthieg/tmp/test-sub/jasmine/output/dist

			jar:

			BUILD SUCCESSFUL Total time: 7 minutes 59 seconds

This command creates jasmine-doc-VERSION.zip , jasmine-jade-VERSION.zip and jasmine-control-VERSION.zip , which contain all the JASMINe binaries (except the UI).

The structure of the jasmine-control.zip file is: 

jonas/
	lib/ext/
		jasmine-shared.jar
	rars/autoload
		drools.rar
	ejb3s/
		jasmine-rules.jar
		jade-ejb.jar
jasmine_rules/
	defaultRules.drl.xml
	test.drl.xml build.xml
README

It contains a build.xml file which will ease the install of the components in a JOnAS server.

The file jasmine-jade.zip contains: 

jade-jmx.zip
jadenode.tgz
jadeboot.tgz
repository/

The use of these files is explained in the user manual.

1.4. Building the UI

To develop or to build the JASMINe UI, you need to have these plugin projects in an eclipse workspace :

They can be found in the SVN server under jasmine/trunk/org.ow2.jasmine.ui/

Open the jasmine.product file from the org.ow2.jasmine.model.diagram project. It's important to take care of selecting all the necessary plug-ins. To launch it from eclipse click on 'Launch the product' on the 'Overview' tab.

You can configure the default connection properties in the configuration/config.ini file.

To get an independent eclipse RCP client, just click on 'Eclipse Product export wizard' on the overview tab of the jasmine.product.

Prev   Next
JASMINe Developer's Guide Home Chapter 2. Introducing JASMINe