-
Notifications
You must be signed in to change notification settings - Fork 403
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
Runtime configuration is resolved in configuration time #129
Comments
Do you have a stack trace from that snippet that points to the code in shadow that is causing the resolution? I can look into it. |
Yes. Here it is: Exception is:
|
Hmm. So this is happening because of trying to calculate if the dependency filter has changed or not from the last execution time...to see if the task is UP-TO-DATE. |
This is fixed with: 5013695 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi!
We use this plugin and it works fine, but currently we have performance issues in our multi-project build, and we started to delay all configuration resolution from Gradle's configuration time to its execution time.
And we bumped into that the shadowJar task causes configuration time resolution of the 'runtime' configuration. Is there any chance to delay this also to execution time?
You can find the hook that we use to hunt for configuration-time resolution: http://discuss.gradle.org/t/slow-compiling-script-into-cache-at-1-build-gradle-per-second/1815/4
Thanks in advance!
The text was updated successfully, but these errors were encountered: