You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Multi module project with different group name and org.gradle.configureondemand=true may cause
../gradlew bootRun
Configuration on demand is an incubating feature.
> Task :server:bootRunMainClassName FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':server:bootRunMainClassName'.
> Could not resolve all files for configuration ':server:runtimeClasspath'.
> Could not find com.example.search:common:0.0.1-SNAPSHOT.
Required by:
project :server
project :server > project :api
When running bootRun task of springboot plugin.
The search-common project and server project has different group.
I also created the issue at gradle side before, and after gradle side's investigation, they suggest me to ask here also.
see gradle/gradle#20377 (comment)
➜ demo-public git:(main) ./gradlew :server:bootRun
Configuration on demand is an incubating feature.
> Task :server:bootRunMainClassName FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':server:bootRunMainClassName'.
> Could not resolve all files for configuration ':server:runtimeClasspath'.
> Could not find com.example.search:common:0.0.1-SNAPSHOT.
Required by:
project :server
project :server > project :api
Below 3 cases works
run ./gradlew :console:run works(application plugin)
Change org.gradle.configureondemand to false works
wilkinsona
changed the title
Configureondemand causes build failure in multi module project with different group name
Enabling configuration on demand causes build failure in multi module project with different group name
Jul 10, 2023
Multi module project with different group name and
org.gradle.configureondemand=true
may causeWhen running bootRun task of springboot plugin.
The search-common project and server project has different
group
.I also created the issue at gradle side before, and after gradle side's investigation, they suggest me to ask here also.
see gradle/gradle#20377 (comment)
Expected Behavior
It works at gradle 7.3 but failed from 7.4
Current Behavior
Failed to run bootRun task.
Context
Steps to Reproduce
Sample project at https://github.com/kojilin/demo-issue
group name of server/console/main is
com.example.server
,search:common iscom.example.search
Below 3 cases works
./gradlew :console:run
works(application plugin)org.gradle.configureondemand
tofalse
worksYour Environment
Build scan URL: https://scans.gradle.com/s/vrgi7ncupnydi
The text was updated successfully, but these errors were encountered: