New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Split liquibase-core and liquibase-commercial jar files #3050
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Conflicts: # liquibase-dist/pom.xml # liquibase-dist/src/main/assembly/assembly-bin.xml
kataggart
added
the
ReleaseMajor
Fix needs to be part of an x.y release, not an x.y.z patch release
label
Jul 11, 2022
Corresponding PRs:
|
Things to test:
|
…0497 # Conflicts: # liquibase-dist/pom.xml
I think this is all working now, including the "re-version" logic. I tested that with a test run of the action. |
suryaaki2
approved these changes
Jul 13, 2022
StevenMassaro
approved these changes
Jul 14, 2022
liquibase-core/src/main/resources/liquibase/examples/start-h2.bat
Outdated
Show resolved
Hide resolved
jnewton03
approved these changes
Jul 14, 2022
…0497 # Conflicts: # liquibase-dist/pom.xml
TEST:
|
Post Release distributions tests pending:
|
# Conflicts: # liquibase-cli/src/main/java/liquibase/integration/commandline/LiquibaseLauncher.java # liquibase-dist/pom.xml
this PR makes me so happy |
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
CodeDistro
DocNeeded
enabler
marketingRequired
ReleaseMajor
Fix needs to be part of an x.y release, not an x.y.z patch release
sprint2022-29
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Impact
Description
Rather than having liquibase-core contain both the functionality from this repository as well as the commercial code, keep "liquibase-core" as the base, open source library and create a new "liquibase-commercial" as the additional proprietary/commercial functionality.
The new liquibase-commercial.jar file will be available:
liquibase-artifacts.zip
andliquibase-artifacts-<BRANCH_NAME>.zip
build artifactsFor consistency, the liquibase-core.jar file will now be stored as
liquibase-core.jar
on the build and release assets pages rather thanliquibase.jar
like it previously was.Impacts
CLI
The liquibase CLI distributions will continue to include both
liquibase-core.jar
andliquibase-commerical.jar
in theinternal/lib
directory**, so there is no impact for CLI users,** regardless of what distribution is used (tar.gz file, zip file, or docker image). The existing liquibase launch scripts have been updated to use the correct jar files.While we will not ship a CLI distribution without
liquibase-commercial.jar
, removing any non-open source code is simply a matter of deletinginternal/lib/liquibase-commercial.jar
NOTE: The
liquibase-core.jar
file was previously calledliquibase.jar
and stored in the root of LIQUIBASE_HOME. So anyone working directly with theliquibase.jar
file will need to update their usage to useinternal/lib/liquibase-core.jar
.NOTE: If you upgrade over an existing LIQUIBASE_HOME installation, the old liquibase.jar file will continue to exist because there is no logic to clean up old files. It can be deleted at your leisure, and it will not be used by Liquibase if left.
Maven Plugin
The Liquibase-maven-plugin will now depend on both
liquibase-core
andliquibase-commercial
instead of justliquibase-core
. This means that anyone using the maven plugin as:will continue to be able to use both free and paid functionality with no changes to their configuration.
Servlet / Spring / Ant Integrations
See "User Managed Dependencies" below
User Managed Dependencies
Any projects that were directly or indirectly referencing or using "liquibase-core" will no longer include the commercial functionality. To continue to use Liquibase Pro features, you need to have both liquibase-core.jar and liquibase-commercial.jar as part of your project.
If you are managing your project using a tools that follows Maven managed dependencies (Maven, Gradle, Ivy, etc.), the easiest approach is to change your dependency on
liquibase-core
toliquibase-commercial
. Because liquibase-commercial defines liquibase-core as a dependency, you will automatically get both included in your project without having to manage multiple dependencies yourself.If you are not directly referencing liquibase-core yourself, but it is comes along as a transitive dependency (like if you use spring-boot), add
org.liquibase:liquibase-commercial
as an additional dependency in your project.