From HemeraBook
Revision as of 16:23, 30 April 2011 by Projettwk (Talk | contribs)

Jump to: navigation, search

Prepare a Workspace

You should begin preparing a workspace with enough space.
Let's call it [HEMERA_ROOT_PATH].

Get Hemera

Hemera user

You can download Hemera binaries from the SourceForge project site:

  • enter the directory of the version you want, and download the Hemera-vX.Y.tgz tarball (X.Y corresponding to the version).
  • uncompress it in [HEMERA_ROOT_PATH]

Hemera developer/contributor

Get the source code

Command line

svn co https://hemerais.svn.sourceforge.net/svnroot/hemerais/trunk/Hemera Hemera

Under Eclipse (or other IDE)

Add https://hemerais.svn.sourceforge.net/svnroot/hemerais as a new repository URL.
Checkout following projects, from trunk or wanted branch: Hemera


Update Operating System

To setup Hemera (e.g. improving accessibility of Hemera binaries/scripts), launch as root superuser:


To help configuring the whole of Hemera, a global configuration file system has been created.

Copy [HEMERA_ROOT_PATH]/config/hemera.conf.sample to [HEMERA_ROOT_PATH]/config/hemera.conf and adapt it to your configuration.
For each tool, you can either update the corresponding configuration element (specifying an absolute path, or a path relative to [HEMERA_ROOT_PATH]) or ensure it is available from the PATH environment variable (specifying only the file name of the tool).


Hemera java pieces require:

-> after installation, you should either update your environment variables JAVA_HOME and ANT_HOME,
   or update environment.java.home and environment.ant.home in your Hemera configuration file.

Java properties

If you want launching Hemera java piece (like the Java sound player) in an IDE (e.g. Eclipse), you should specify the following properties:

  • java.system.class.loader to define the Hemera specific classloader which loads the properties file automatically
  • hemera.property.file to define the Hemera properties file

For instance (with Eclipse ${workspace_loc} variable):

-Djava.system.class.loader=hemera.HemeraClassLoader -Dhemera.property.file=${workspace_loc}/hemera/config/hemera.conf

You may use the additional properties:

  • hemera.log.file to define a log file (messages will be appended to the file if it already exists)

For instance:


Third-Party tools availability

See Install third-party tools.
Each third-party tool binary path, and data file path are checked when using corresponding core module.
A specific error message will be given in case of failure.