If you got a patch for an open issue you can attach it in JIRA.
"camunda" wrote:As for the version issue, I haven't had a chance to look at JBPM 4 at all, but I'm assuming it can be adapted for it. In any case, it's exists in our code base as a standalone component, so it could always be release as a separate download for those using version 3.
Ideed, I think thats the best solution.
jbpm 4 has changed in this area a lot, so changing the process instance version is very different, but much easier as well...
Have a look in the jbpm 4.2 release notes, the according JIRA issue should be linked there.
I think the only related thing at release notes is https://jira.jboss.org/jira/browse/JBPM-165, but it doesn't seem an actual resolution of this problem.
Ok, ok, it's documented at the developer guide, 2.6. I was only looking at user guide, but it seems neccesary using both. I'll have a deep look at it.
Than you!