Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

set affectedTestConfiguration globally #62

Closed
xmlking opened this issue Jun 25, 2021 · 3 comments
Closed

set affectedTestConfiguration globally #62

xmlking opened this issue Jun 25, 2021 · 3 comments

Comments

@xmlking
Copy link

xmlking commented Jun 25, 2021

I cannot set like this in project root's build.gradle.kts file.

subprojects {
   affectedTestConfiguration { jvmTestTask = "test" }
}

all my subprojects are java, it would be nice if we can set this at one place instead of forced to add affectedTestConfiguration { jvmTestTask = "test" } to every subprojects

my multi-module project : https://github.com/xmlking/micro-apps

@xmlking
Copy link
Author

xmlking commented Jun 25, 2021

b.t.w
after adding this plugin, I am getting weird errors

 gradle :apps:wordcount-pipeline:build
Type-safe dependency accessors is an incubating feature.
Type-safe project accessors is an incubating feature.
Configuration on demand is an incubating feature.

> Configure project :
Version: 1.6.5-SNAPSHOT,  Branch: develop, isCI: false
SpotlessChangelog Version Next: 1.7.0-SNAPSHOT  Last: 1.6.4

FAILURE: Build failed with an exception.

* What went wrong:
Could not determine the dependencies of task ':apps:wordcount-pipeline:javadoc'.
> Could not resolve all dependencies for configuration ':apps:wordcount-pipeline:compileClasspath'.
   > A problem occurred configuring project ':libs:core'.
      > org.gradle.api.internal.initialization.DefaultClassLoaderScope@1837acb2 must be locked before it can be used to compute a classpath!

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

@xmlking
Copy link
Author

xmlking commented Jun 25, 2021

ignore the above error.
I enabled new on-demand configuration option org.gradle.configureondemand=true in gradle.properties which caused above error.

@chris-mitchell
Copy link
Contributor

It sounds like this error has been resolved with #62 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants