Migration from 6.1.2 to 6.2.1

Hello. We have just completed beta version for Flowable 6.2.1 and Liferay 7 integration module. During migration we found out one issue that prevented us from deployment into Liferay OSGi(Equinox) - db package names in 2 different modules are the same: https://github.com/flowable/flowable-engine/tree/flowable-6.2.1/modules/flowable-engine/src/main/resources/org/flowable/db and https://github.com/flowable/flowable-engine/tree/flowable-6.2.1/modules/flowable-engine-common/src/main/resources/org/flowable/db though we have to rename package name for flowable-engine-common in our fork. So I wonder - are you planing to change package name in some of this 2 modules or it will remain the same? Thanks.

Looks like this was missed during the package refactoring in 6.2.0 (see: http://www.flowable.org/blog/2017/10/13/flowable-6.2.0-release.html for details).

I believe you should create an issue for this at: https://github.com/flowable/flowable-engine/issues

Thanks Pascal,
I’ve posted a new issue with magic id: https://github.com/flowable/flowable-engine/issues/777

That indeed doesn’t seem right. I wonder why the osgi tests haven’t caught this. We’ll look into it.