Home arrow BPM & Open Source arrow project details
tk4jbpm project details Drucken

Currently the project moves to sourceforge, to get a better infrastructure. The migration should be finished at the end of june 2007. Also we use Maven2 now for the project to have a better control over dependencies.

Getting and using sources

Subversion 

You can get the sources via Subversion, all necessary details are on the sourceforge site: http://sourceforge.net/projects/tk4jbpm/

Maven2 

The project is done with Maven2. Maven download the most of the dependencies for the project itself, but unfortunatly, not all libraries are available in a Maven2 repository, so we provide the other libs in the Subversion repository. You have to import these manually to Maven2. You find a file called "import-maven-libs.txt" in the root directory, there all necessary commands are listed, to import the camunda commons for example, you need the following command:

mvn install:install-file -DgroupId=com.camunda -DartifactId=commons /
    -Dversion=1.0 -Dpackaging=jar -Dfile=libs/camunda-commons.jar

After importing the libraries you can use the known Maven2 goals, for example:

  • compile
  • package 

Eclipse

To generate a working eclipse project just use the Maven2 Eclipse plugin:

mvn eclipse:eclipse

After that, you can import the project into your eclipse. If you don't have it, you have to configure a variable M2_REPO which points to you local Maven2 repository.

See the "Guide to using Eclipse with Maven 2.x" for more details.

Mailinglist

For the project we use the sourceforge mailinglist, you can subscribe or unsubscribe here: tk4jbpm-user mailinglist

Team & Contributing

Portrait Bernd Rücker

Project lead is me, Bernd Ruecker.

I am happy about everybody who wants to contribute. Please contact me via Diese E-Mail Adresse ist gegen Spam Bots geschützt, Sie müssen Javascript aktivieren, damit Sie sie sehen können .


Links

Status

  • The current version of the toolkit runs with jbpm 3.2 only (because we refactored everything to use the standatd jbpm command pattern).
  • The project is used in different real life projects by now, but normally integrated very much. So it is currently not really a out of the box solution
  • After the big refactoring to work with jbpm 3.2, some testing effort needs to be done, but has not finished yet