grails-data-hibernate5-dbmigration only requires grails-shell-cli during development
- Dominant language
- Groovy
- Stars
- 2.9k
- Forks
- 975
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 92
Description
grails-shell-cli adds ~49 jars and ~20MB of jar/war
grails-shell-cli can be excluding from the jar/war and databasemigration.updateOnStart works without issue
```
developmentOnly "org.apache.grails:grails-data-hibernate5-dbmigration"
runtimeOnly "org.apache.grails:grails-data-hibernate5-dbmigration", {
exclude group: 'org.apache.grails', module: 'grails-shell-cli'
}
```
```
java -jar .\build\libs\database-migration-test-0.1.jar
> <
> ____ _ _ <
> / ___|_ __ __ _(_) |___ <
> | | _| '__/ _` | | / __| <
> | |_| | | | (_| | | \__ \ <
> \____|_| \__,_|_|_|___/ <
> https://grails.apache.org <
> <
UPDATE SUMMARY
Run: 2
Previously run: 0
Filtered out: 0
-------------------------------
Total change sets: 2
Grails application running at http://localhost:8080 in environment: production
```
Contributor guide
Research direction
Start by inspecting the dependency declarations for grails-data-hibernate5-dbmigration and the sample application's runtime packaging. Reproduce the executable JAR with databasemigration.updateOnStart enabled, then verify that grails-shell-cli is absent from the packaged JAR/WAR while the migration runs successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100