Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  1. Check out the latest version from Github (more details see
  2. Go into the distro subfolder and run the following ant command: 'ant clean distro'
  3. The distribution can now be found in the target folder.

Setup scripts in the distro

After an distribution is unzipped (or directly in the distro/target/activiti-version directory), a number of scripts are offered to our users as well. Those scripts can be found in [activiti.home]/setup/build.xml and can optionally use settings from [user.home]/.activiti/

As an example, here's the content of my [user.home]/.activiti/

Code Block

activiti.home, is used in the setup/build.xml. It will work straight from the sources. So you can add the setup from the sources to your ant view in your IDE.

downloads.dir, is used in the setup/build.xml. It allows you to configure a custom location for your directory to download/find tomcat. If you don't specify this, the default is relative to the setup directory (../downloads). So if you use the setup/build from the sources, you might end up downloading tomcat into your sources. If that still would happen, don't check it in! (wink)

tomcat.enable.debug is used in setup/build.xml when Tomcat is installed. If the property is specified (whatever value), the parameter 'jpda' will be added to the start commands in Tomcat's '' and 'startup.bat' scripts. That will cause the remote debugging service to listen on port 8000.

skip.deploy.activiti.modeler=true set this property if the Activiti Modeler fetching from net and deployment must be skipped.
Unless before a release or explicitly working on the Activiti Modeler, it's advised to set this property since sometimes a version matching the current trunk version isn't uploaded yet, causing the demo setup to fail.
mvn.executable=mvn.bat on windows you have to set this property to make the calls from the ant build scripts (distro/build.xml and qa/build.xml) to maven work. To work with Activiti Modeler or Activiti Cycle on trunk, set the property in your [user.home]/.activiti/ to, e.g., if you want to use a previous release or something like file:///home/falko/svn/activiti-modeler/dist/activiti-modeler.war if you want to use an own build of the Activiti Modeler.

linux.browser=echo: Set this poperty to echo to prevent the browser from being opened. You also use a different browser than Firefox through this property.

[user.home]/.activiti/tomcat-users.xml To enable the automatic redeployment targets in qa/build.xml, put a tomcat-users.xml in your [user.home]/.activiti directory with the following content:

Code Block
  <?xml version="1.0" encoding="utf-8"?> 
    <role rolename="manager"/> 
    <user username="activiti" password="activiti" roles="manager"/> 

Eclipse IDE Setup

In order to have BPMN code completion and validation, import BPMN's XML Schemas from activiti-engine/src/main/resources/org/activiti/impl/bpmn/parser into the Eclipse XML Catalog, which can be found in Preferences --> XML --> XMLCatalog.


More about the QA and CI infrastructure can be found here: QA and CI Guide

Demo setup

To run smoke tests on webapps, the quickest way to get started is using the target test.demo.setup in qa/build.xml
That will also startup h2 and tomcat. So to rebuild, you can use the target test.demo.setup.refresh That target will first shutdown tomcat and h2 and then do a full new demo test setup.
Building the javadocs

Use target build.javadocs in qa/build.xml

Debugging ant task

GIT pointers

Typical initial setup: