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
Gradle fails when no incremental compile snapshot data available #6612
Comments
@oehme Could you please check if this could be related to incremental compilation? |
I already fixed this on master, can you try with the nightly? The culprit is a discrepancy between the project cache dir and the user home cache dir. It happens if you build the same project with different user homes. Deleting the |
I wonder how widespread this is and if we should do a 4.10.1 with the fix (which is trivial). |
Given that 4.10 is to be the last 4.x I would do so, though we may wait a bit more just in case something else pops up. |
I've changed the target milestone and cherry-picked the fix to |
We have exactly the same problem in a big multi-project build. Would disabling the incremental Java compilation work too?
|
@bronogard Yes, but make sure to revert that once 4.10.1 is out :) |
@oehme Perfect, thanks we will do that as soon as 4.10.1 is out. ^^ |
oh, same issue. waiting 4.10.1 |
Gradle 4.10 seems to have introduced a regression...
Expected Behavior
Build should not fail and doesn't fail with Gradle 4.9.
Current Behavior
Build failure:
Context
We had to revert back to Gradle 4.9 for the time being.
Steps to Reproduce (for bugs)
I had no luck reproducing this issue in an isolated example project, unfortunately.
The problem may be related to a dependency that is both a build-internal dependency as well as a transitive dependency, i.e. once referenced via
project(..)
but also referenced viagroup:artifact:version
. But this is only a guess...I hope the stacktrace is sufficient since it doesn't make sense that the build would fail in case of a cache miss.
Your Environment
I can't provide you with a build scan.
The text was updated successfully, but these errors were encountered: