What are the implications of the Liquibase licensing changes? #43226
-
|
I see that Liquibase are changing their license from Apache 2.0 to Functional Source License (FSL): Presumably Keycloak will be sticking with Apache 2.0 so how will this work? Will the project stick on an older version of Liquibase? Or move to Flyway? Or something else? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
From my understanding FSL does not restrict Keycloak from including/using Liquibase; as Keycloak is not a commercial product and nor does it compete with Liquibase. |
Beta Was this translation helpful? Give feedback.
-
|
I've reached out to the CNCF to get an opinion from the license experts: |
Beta Was this translation helpful? Give feedback.
-
|
My initial thoughts on this was naive, and this is going to be a big issue. Not sure what we will do, but created an GitHub Issue to track it here #43391 One thing is certain though we will find a solution it just might take more effort than we'd like :/ |
Beta Was this translation helpful? Give feedback.
My initial thoughts on this was naive, and this is going to be a big issue. Not sure what we will do, but created an GitHub Issue to track it here #43391
One thing is certain though we will find a solution it just might take more effort than we'd like :/