Hi Carl, This is likely a bug due to reworking the Gradle plugins to support lazy. I've seen this occur before when the gradle cache is cached. Can you please try running your build with '--info' on it? Look for the 'FindMainTask' and see if it says 'FROM-CACHE' or 'UPTODATE'. If you can confirm this and include the log snippet from the find main task, I can help troubleshoot further.
Regards, James On 2025/06/14 21:33:35 Carl Marcum wrote: > Hi All, > > I'm having an issue running a web plugin created from Grails Forge. > > Looks like I'm not getting the resolvedMainClassName file like with a > web application. > > Created for Grails 7.0.0-M4, Java 21, Hibernate, Tomcat, and Spock. No > additional plugins. > > ./gradlew bootRun > > Task :bootRun FAILED > > [Incubating] Problems report is available at: > file:///.../demo-plugin/build/reports/problems/problems-report.html > > FAILURE: Build failed with an exception. > > * What went wrong: > A problem was found with the configuration of task ':bootRun' (type > 'BootRun'). > - In plugin 'org.springframework.boot.gradle.plugin.SpringBootPlugin' > type 'org.springframework.boot.gradle.tasks.run.BootRun' property '$1' > specifies file '/.../demo-plugin/build/resolvedMainClassName' which > doesn't exist. > > Reason: An input file was expected to be present but it doesn't exist. > > Let me know if you have any ideas. > > Thanks, > > Carl > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
