-
Notifications
You must be signed in to change notification settings - Fork 201
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
Lots of java.lang.IllegalStateExceptions logged with Gradle 3.4-rc-1 #125
Comments
From Gradle's source code, it appears that we should filter the configurations by checking isCanBeResolved() first. |
Or it may be that we want to resolve them, since they appear to be api/impl separations. If a clone and |
The configurations come from the new |
Closing in favor of #131 |
When running the
dependencyUpdates
task with Gradle 3.4, I get a lot of log output:When running with
-i
, the stacktraces are logged too:Not sure what changed inside Gradle, but I guess there needs to be an additional check as to whether the current configuration is "internal".
The text was updated successfully, but these errors were encountered: