-
Notifications
You must be signed in to change notification settings - Fork 115
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
When to support grails 3.3? #141
Comments
Have you been aware of this? |
@kevinclcn Have you tried version 3.0.3 of the plugin? As far as I can tell it's fixed there |
hi @jameskleeh , I created a demo for this issue: https://github.com/kevinclcn/dbmigrationIssue clone it and run
But once I commented out the second datasource(the app datasource in application.yml), the migration works fine. I problem I found is in the method DatebaseMigrationCommand::getDataSourceConfig(), see the pr: https://github.com/grails-plugins/grails-database-migration/pull/140/files |
We are having the same issue, the application starts up and runs migrations ok but commands like |
Actually, the problem is that the commands have their own config helper:
Which isn't aware of the new syntax. When the application is bootstrapped the dataSource is injected but for the commands it tries to resolve it incorrectly. |
Steps to Reproduce
Per this link grails/gorm-hibernate5#25, the correct multiple datasources config syntax for grails 3.3 is:
rather than:
But the grails-database-migration tool supports only the second format. I've tried to provide a PR for quick fix, but it broken lots of tests since grails 3.3's test framework has been changed totally. #140
The text was updated successfully, but these errors were encountered: