Hi, I have a grails application that I have recently upgraded from 5.3.6 to 6.2.0 The upgrade all worked fine, except for one issue, whereby although the app ran fine via gradle bootRun or running tests, but when deployed in tomcat the webapp was not recognised (Tomcat did not start it). With further investigation, it appears that the BootInitializerClassInjector AST Transformer in grails-web-boot is not running at compile time, and is not creating the ApplicationLoader class to go with my Application class - it is missing from the war file. If I modify my Application during runtime in dev mode, then I can see the BootInitializerClassInjector is running, and creating the ApplicationLoader - but not if I do a clean and then build a war file. I cannot see any messages/errors when compiling. I can manually create an ApplicationLoader class, with the same code as would be created by BootInitializerClassInjector, and when I do this, everything works find in tomcat. But this doesn't feel like the right solution. As this is a fairly large multi-module grails project, I'm sure this must be due to some missing configuration, or similar, but I cannot find where this might be (I have compared all major config, definition of Application class, dependencies, etc against a freshly created 6.2 webapp) Does anyone know what this might be, or can anyone point me towards where I should be looking to try & debug/diagnose this? (not a big expert on writing/debugging AST Transformations). Many thanks in advance for any advice.

Are you building the war with

gradle assemble

? And does bootStartScripts complete*?* 103434 PM: Executing 'assemble'... Starting Gradle Daemon... Gradle Daemon started in 1 s 241 ms

Task :clearBuildDir

Task :assetCompile

Task :compileJava NO-SOURCE

Task :compileGroovy

Task :generateGitProperties FROM-CACHE

Task :buildProperties

Task :processResources

Task :classes

Task :bootWarMainClassName

Task :compileWebappGroovyPages NO-SOURCE

Task :compileGroovyPages

Task :bootWar

Task :*bootStartScripts*

Task :bootDistTar

Task :bootDistZip

Task :jar

Task :*startScripts*

Task :distTar

Task :distZip

Task :war

Task :assemble

BUILD SUCCESSFUL in 42s 10 actionable tasks: 9 executed, 1 from cache 103516 PM: Execution finished 'assemble'.

I don't have the bootStartScripts stage executed at all, which is presumably the issue: > Task IotaacompileAstJava NO-SOURCE > Task IotaacompileAstGroovy NO-SOURCE > Task IotaaastClasses UP-TO-DATE > Task IotaacompileJava NO-SOURCE > Task IotaacopyAstClasses NO-SOURCE > Task IotaacompileGroovy > Task Iotaaclasses > Task IotaacompileWebappGroovyPages NO-SOURCE > Task IotaacompileGroovyPages > Task Iotaajar > Task PumpHouseassetCompile > Task PumpHousecompileAstJava NO-SOURCE > Task PumpHousecompileAstGroovy NO-SOURCE > Task PumpHouseastClasses UP-TO-DATE > Task PumpHousecompileJava NO-SOURCE > Task PumpHousecompileGroovy > Task PumpHousecopyAstClasses NO-SOURCE > Task PumpHouseclasses > Task PumpHousebootWarMainClassName > Task PumpHousebootWar > Task PumpHousewar > Task PumpHouseassemble

Which generated lib or distribution are you using from the build directory? plain or boot? When you say Tomcat, is that Tomcat provided by your server instance or are you using the boot war which includes Tomcat? There are a ton of combinations, so just trying to understand yours. I personally deploy on AWS Elastic Beanstalk with the Java SE Platform (Not Tomcat), use the generated boot war and it is started with

java -jar admin.war

I'm trying to create a war file to use within a standalone tomcat.

Does your Application class extend GrailsAutoConfiguration?

import grails.boot.GrailsApp
import grails.boot.config.GrailsAutoConfiguration
import groovy.transform.CompileStatic

@CompileStatic
class Application extends GrailsAutoConfiguration {
    static void main(String[] args) {
        GrailsApp.run(Application, args)
    }
}

yes, the Application class does extend GrailsAutoConfiguration:

class Application extends GrailsAutoConfiguration {

static void main(String[] args) {

GrailsApp.run(Application, args)

}

If I alter this class at runtime in dev mode, I can see the BootInitializerClassInjector running and creating the ApplicationLoader for this class in the debugger - it's as if it's generally ok, but the ast transformation is not being run at all during compilation/build.