<@U073AUX1J0L> Your fix for <https://github.com/ap...
# questions
s
@James Fredley Your fix for https://github.com/apache/grails-core/issues/15078 just reminded me to check one of my apps to see if I had the same issue in RC2. I noticed something else whether this is intentional or not. Adding the migration plugin adds an extra 49 jars to the war file (tested on your example project attached the the above issue). It seems the migration plugin is pulling in the grails-shell-cli which in turn is pulling in a lot of dependencies. Is the grails-shell-cli required at runtime?
j
Historically database migration required shell-cli for the scripts. I don't know if it required at runtime after all the changes we made. What the difference in jar/war size with and without?
88,796,091 bytes vs 69,352,946 bytes
This looks promising.
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'
}
Copy code
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