[GRADLE-1049] updated remote snapshot artifact during multiproject build causes exception Created: 22/Jul/10 Updated: 04/Jan/13 Resolved: 29/Jan/12
|Reporter:||René Gröschke (Inactive)||Assignee:||Daz DeBoer|
If you run a multiproject build and different subprojects have dependencies to the same artifact that is stored in a remote repository, the build fails if the remote artifact was updated while running the multiproject.
The stacktrace looks like this:
09:14:09.609 [main] ERROR org.gradle.logging.IvyLoggingAdaper - Couldn't delete outdated artifact from cache: C:\Dokumente und Einstellungen\Hudson\.gradle\cache\org.acme\SimpleConfiguration\jars\SimpleConfiguration-0.8-SNAPSHOT.jar
09:14:09.609 [main] INFO org.gradle.logging.IvyLoggingAdaper -
Gradle should always resolve a dynamic dependency to exactly the
|Comment by Hans Dockter [ 22/Jul/10 ]|
Your issue should be fixed in trunk for all practical purposes (I guess you are using preview-3). Ivy (and thus preview-3) always checks Maven snapshots for being up to date. This can cause trouble and is a big performance issue. In trunk the up to date check for snapshots is now configurable (default is daily). Unless you are doing a build around midnight, everything should work fine.
But I don't close the issue as we want to have a more bullet proof solution for one instance of a multi-project build.
|Comment by Thomas Glaeser [ 03/Dec/10 ]|
This has become a critical issue for us. Are there any setting/workarounds that could prevent this issue?
|Comment by René Gröschke (Inactive) [ 28/Jan/11 ]|
just ran into this issue again with 0.9.1
|Comment by René Gröschke (Inactive) [ 31/Jan/11 ]|
Is there a more elegant way to customize Ivys DefaultRepositoryCacheManager via gradle?
|Comment by René Gröschke (Inactive) [ 02/Mar/11 ]|