On 20/07/10 6:39 AM, Rene Groeschke wrote:
Hi John,
I think the issue I'm running into is not GRADLE-949. 949 describes,
that the cache isn't updated even though a new snapshot was pushed to
a remote repo. My problem is, that gradle detects correctly that a new
snapshot is available, but the downloaded file cannot be stored in the
cache, because the old artifact cannot be deleted (see my previous
posted error message) I tried to reconstruct the described problem
this evening on my mac, but I wasn't able to reproduce it. Maybe it's
a OS (Windows) related problem.
On Windows, you get the failure, because the old file cannot be deleted
from the cache. On other platforms, a new snapshot gets silently swapped
in. I don't think either behaviour is really very good.
I think Gradle should always resolve a dynamic dependency to exactly the
same set of artifacts during the entire life of the build, regardless of
which project or configuration the dependency is included in.
regards,
René
Am 19.07.10 20:01, schrieb John Murph:
Do you think this might be caused by GRADLE-949
<http://jira.codehaus.org/browse/GRADLE-949>? Is so, Hans recently
(July 9th) pushed a fix for it to git.
--
John Murph
Automated Logic Research Team
--
------------------------------------
Rene Groeschke
[email protected]
http://www.breskeby.com
http://twitter.com/breskeby
------------------------------------
--
Adam Murdoch
Gradle Developer
http://www.gradle.org
CTO, Gradle Inc. - Gradle Training, Support, Consulting
http://www.gradle.biz
