db migration commands results in errors when using inline/exploded plugins
- Dominant language
- Groovy
- Stars
- 2.9k
- Forks
- 975
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 92
Description
When a project uses any plugin as exploded as below
```
grails {
exploded = true
plugins {
compile project(':inline-plugin')
}
}
```
Db migration will try to run the commands on the plugin too, and will fails with error
Try with attached example
[bugwork.zip](https://github.com/grails-plugins/grails-database-migration/files/1104249/bugwork.zip)
run the grails dam-generate-gorm-changelog on the app and u should see the error.
Contributor guide
Research direction
Download and run the attached bugwork.zip example, then execute grails dam-generate-gorm-changelog on the app with the inline plugin configured as exploded. Trace why the migration command runs against the plugin and verify the command completes without the reported error while handling the plugin correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100