The GitHub Actions job "CI - Groovy Joint Validation Build" on grails-core.git/feature/gsp-compile-static-8.0.x has succeeded. Run started by GitHub user codeconsole (triggered by codeconsole).
Head commit for run: 197408ae16fa66f63de8a1ee5ba7f7fd77c7b41f / Scott Murphy Heiberg <[email protected]> Add a build option for compiling pages statically grails.views.gsp.compileStatic could only be stated in configuration, so a project keeping its build options together had nowhere to put it. Add it to the compileStatic block the artefact opt-ins already live in: grails { compileStatic { gsp = true } } It states the setting that already exists rather than introducing a name of its own, as a system property, which reaches both places a page is compiled: the forked compiler the build runs, and the JVM running the application, which compiles a page again when it changes. Reaching only the first would mean a page compiled one way while being developed and another when packaged, which is worse than not offering the option. The parser reads the property after configuration and lets it replace what configuration said, matching the order a system property takes over application.yml in the running application; a page directive is read afterwards and still decides for the page carrying it. Not included in `all`. The artefact opt-ins fail on code that is doubtful anyway; this fails on a page reading a model variable it has not declared, which describes most pages in an application that has never declared one. Report URL: https://github.com/apache/grails-core/actions/runs/31626600429 With regards, GitHub Actions via GitBox
