Liquibase 5.0 has been released [1] and has changed its license to Functional Source License. Can/should Spring Boot provide auto configuration for that version, or will the auto configuration machinery be removed since 4.x might be unmaintained as of now?
[1] https://docs.liquibase.com/community/release-notes/5-0
Comment From: wilkinsona
Thanks for bringing this to our attention. This will almost certainly be a problem, in the short term at least, as I cannot find any information about compatibility between our Apache license and the FSL. It reads to me like it should be OK, but IANAL. I think we'll have to talk with legal about this which will, at best, delay an upgrade to Liquibase 5.
@filipelautert can you share any information about plans for ongoing maintenance of Liquibase 4.x or Liquibase's opinion on the compatibility of the Apache and FSL licenses?
Comment From: filipelautert
@filipelautert can you share any information about plans for ongoing maintenance of Liquibase 4.x or Liquibase's opinion on the compatibility of the Apache and FSL licenses?
Hello @wilkinsona ! Functional Source License (FSL) is not OSI-approved open source, but it is free to use, share, and modify for internal projects. The main restriction is on reselling Liquibase as a service. Using Liquibase within an application, including Spring Boot auto-configuration, is allowed under the license. That said, only legal team can give a definitive view on compatibility between Apache and FSL, so we recommend confirming with them as you mentioned .
From an engineering POV, what I can say is that we have plans to improve and modernize Liquibase compatibility and features with Spring Boot soon, so I don't see why we would cause you trouble.
We were not thinking about ongoing maintenance of Liquibase 4.x yet . But as we already received this feedback in some locations, I'm taking this idea to management and will keep you posted.