Hi James,
After cleaning and running with: ./gradlew --info --console=verbose bootRun
> Task :classes
Skipping task ':classes' as it has no actions.
Resolve mutations for :findMainClass (Thread[#647,Execution worker
Thread 7,5,main]) started.
:findMainClass (Thread[#647,Execution worker Thread 7,5,main]) started.
> Task :findMainClass UP-TO-DATE
Custom actions are attached to task ':findMainClass'.
Build cache key for task ':findMainClass' is
2c527b3ddffef7c5e37a87c952814d20
Skipping task ':findMainClass' as it is up-to-date.
Resolve mutations for :bootRun (Thread[#647,Execution worker Thread
7,5,main]) started.
:bootRun (Thread[#647,Execution worker Thread 7,5,main]) started.
> Task :bootRun FAILED
After cleaning and running with: ./gradlew --rerun-tasks --info
--console=verbose bootRun
> Task :classes
Skipping task ':classes' as it has no actions.
Resolve mutations for :findMainClass (Thread[#841,Execution
worker,5,main]) started.
:findMainClass (Thread[#841,Execution worker,5,main]) started.
> Task :findMainClass
Custom actions are attached to task ':findMainClass'.
Build cache key for task ':findMainClass' is
2c527b3ddffef7c5e37a87c952814d20
Task ':findMainClass' is not up-to-date because:
Executed with '--rerun-tasks'.
There is neither a bootJar or bootWar task that will run. Skipping
finding main Application class.
Stored cache entry for task ':findMainClass' with cache key
2c527b3ddffef7c5e37a87c952814d20
Resolve mutations for :bootRun (Thread[#841,Execution worker,5,main])
started.
:bootRun (Thread[#841,Execution worker,5,main]) started.
> Task :bootRun FAILED
I hope this is what you were looking for.
Please let me know if I need to provide more.
Best regards,
Carl
On 6/16/25 10:18 AM, James Daugherty wrote:
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
