jamesfredley commented on issue #14035: URL: https://github.com/apache/grails-core/issues/14035#issuecomment-3215153224
@boardbloke My first thought was this is something docker is doing to the war contents based on what we saw on https://github.com/wondrify/asset-pipeline/issues/373 and after removing docker from the equation, which I always take as a first step, I think docker is the difference. Please take a look at /WEB-INF/classes/ and see if `application.groovy` and `application.yml` are present after running `docker build -t badapp:0.2-SNAPSHOT ./docker` locally I tested this with `bootRun` and with `bootWar` + `java -jar badapp-0.2.war` after changing the following in application.yml ``` production: dataSource: dbCreate: create-drop url: jdbc:h2:mem:prodDb;LOCK_TIMEOUT=10000;DB_CLOSE_ON_EXIT=FALSE ``` Both save two `Example` instances with application.groovy as is and both only save one `Example` instance with application.groovy commented out. That confirms that application.groovy appears to be the variable, but given this works with `bootRun` and with `bootWar` + `java -jar badapp-0.2.war`, see what docker is doing as a first step. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@grails.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
