As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.
When encountering a bug in Activiti, the easiest way to reach the Activiti team and see it fixed is to create an issue in the Activiti Jira (http://jira.codehaus.org/browse/ACT).Of course, a good description on how to reproduce the problem is crucial. But to make it really interesting for us (and to speed up things), the issue is accompanied by a unit test demonstrating the problem.To simplify this process, we've created a 'unit test template' project which you can use: https://github.com/Activiti/activiti-unit-test-templateAdd your failing unit test, zip up the project and attach it to the issue.More about this template, read http://www.jorambarrez.be/blog/2012/09/24/how-to-write-a-unit-test/
<dependency><br> <groupId>org.slf4j</groupId><br> <artifactId>slf4j-log4j12</artifactId><br> <version>1.7.2</version><br></dependency>
I've updated the template to fix the logging: https://github.com/Activiti/activiti-unit-test-template/commit/a6b347263362d9b5385b81bd96cca225d2e16843
org.activiti.engine.impl.test.JobTestHelper#waitForJobExecutorOnCondition(org.activiti.engine.ProcessEngineConfiguration, long, long, java.util.concurrent.Callable<java.lang.Boolean>)