Split liquibase-core Jar into community and pro parts

Description

We run into problems due to name conflicts on implementations of interface liquibase.change.Change. Obviously the names used of the pro version conflict with those of extensions, since the pro implementations are considered with a higher priority.

Since we neither can switch to the pro version nor revised the use of those changes we stick to a version before 3.8.0. If the pro stuff would be shipped in a separate jar, we won't run into these problems. Another solution would we to skip those internal pro implementation if no license is found.

Environment

liquibase-core-3.8.5 Java11

Activity

Show:
Filip Hrisafov
February 19, 2020, 9:31 PM

I think that this is related to as well

Reporter

B

Affects versions

Priority

Blocker
Configure