This message is primarily for people working on code that has jBPM dependencies.

This Friday, we will be fixing the "split packages" problem in jBPM. Fixing this problem will make a number of other projects that use or can use jBPM happy (fuse/karaf/camel/switchyard) as well as make OSGi/jigsaw use with jBPM (more) possible.

The changes that we will be making are luckily only related to the human-task code and the new (human-task) services.

The freeze on the jBPM code will start this coming Friday (22nd) at 6.00 CET/0.00 EST.
I expect it to be unfrozen by, at the latest, 17.00 CET/11.00 EST.

This will probably also mean a freeze on the (jbpm related parts of) droolsjbpm-integration, droolsjbpm-tools and possibly guvnor. Because the changes are limited to the human-task code, I'm not even sure if freezes on these projects are necessary and will be sending up a follow up e-mail about that.

If this is a problem for you or you otherwise think that this should not be done then, please let me know!
Because of release deadlines for 6.x, it's important to get this done soon.

Thanks,
Marco

-- 
jBPM/Drools developer
Utrecht, the Netherlands