This repository was archived by the owner on Mar 13, 2025. It is now read-only.
Merge database migration plugin into gorm-hibernate5 #959
Conversation
This file contains hidden or 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
…2-1.x Update dependency com.h2database:h2 to v1.4.200
…asciidoctor-gradle-plugin-1.x Update dependency org.asciidoctor:asciidoctor-gradle-plugin to v1.6.1
Remove provided scope as it is deprecated
Migrated to Grails 5
Remove spock-outputcapture dependency
Update dependency org.hibernate:hibernate-core to v5.6.1.Final
… classes Liquibase 4.0 has changed the way to load the extension classes from Java classloader interfaces to java.util.ServiceLoader system. See Liquibase 4.0 extension upgrade guide at https://docs.liquibase.com/tools-integrations/extensions/extension-upgrade-guides/lb-4.0-upgrade-guide.html
Fix breaking API changes
To capture output from System.out and System.err as the one from Spring Liquibase API does not work with Spock and JUnit5
to ignore log files
…ersion Update dependency org.liquibase:liquibase-core to v4 - manual
To correctly resolve next version based on labels
Update Release Drafter Configuration
Update dependency asciidoctor-gradle-plugin:1.6.2 to org.asciidoctor:asciidoctor-gradle-jvm:3.3.2
To correctly resolve the tag and name based on RESOLVED_VERSION
Update release-drafter.yml
Add a new category "Build/CI" to release notes
Update README.md for 5.0.0 release
# Conflicts: # build.gradle # gradle.properties
Merge 5.0.x into 6.0.x
back to grails 7.0.0-SNAPSHOT
docs: mentioned that the placement of sourceSets affects Grails 4 and above (cherry picked from commit 4cc66c98068f17dea83e58839fb246230949f305)
Merge pull request #397 from MichaelMorett/feature/fix-getting-started
…erge-database-migration-plugin
|
|
jdaugherty
approved these changes
Feb 20, 2025
Contributor
|
After we merge this, we should add a readme to the default branch in grails-database-migration repo to say it moved here. We then should transfer relevant issues and mark them for the plugin. I can help with both of these if you'd like. |
# Conflicts: # gradle.properties
Contributor
Author
|
@jdaugherty Yes, please proceed with the readme and issue transfer. I just resolved the merge conflict and will merge as soon as everything passes. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
https://github.com/grails/grails-database-migration
grails-database-migration is dependent upon liquibase-core and liquibase-hibernate5. Given the dependency on liquibase-hibernate5 the historical version of grails-database-migration is being merged into the gorm-hibernate5 project, since they are tied at the hip by hibernate5. The current release of https://mvnrepository.com/artifact/org.liquibase.ext/liquibase-hibernate5/4.27.0 may be the last hibernate5 Liquibase release given the Apr 03, 2024 release date.
For this merge the maven coordinates will stay org.grails.plugins:database-migration, but the version will jump from 6.0.x to 9.0.x to match GORM and make it easier to confirm compatibility.
When gorm-hibernate6 is ready, a distinct version of database-migration should be merged into that project which supports hibernate6. It should have a distinct artifactid, such as database-migration-hibernate6.