The knowledge-api module (which is necessary to support backwards compatibility with the drools5 and jbpm5 api) should be included in the b*ms-engine.zip. Or do we want it to only be included as a separate jar (for example together with the jcr repo migration tooling)?
I would like to see it work out of the box with a few demos I plan to provide detailing how this works. That is my vote.
master: http://github.com/droolsjbpm/droolsjbpm-integration/commit/32edd132b 6.0.x: http://github.com/droolsjbpm/droolsjbpm-integration/commit/bcbcb6212
Verified in BPMS 6.0.0.ER4 The knowledge API is included in the bpms-engine.