Unfortunately, the problem still exists.
I noticed that gradle uploads artifacts UTC/GMT timezone (UTC/GMT) while
we are one hour ahead. However, on download gradle seems to use the
local timezone to compare times which makes gradle believe in certain
situations that a jar has not been updated.
Example:
* Project A depends on Project B ( A->B )
* Local timezone: UTC + 1h
* gradle dependencies is executed on project A at 10:05 UTC (11:05 local
time). A new snapshot gets fetched.
* gradle uploadArchives is executed on project B at 10:30 UTC, a new
snapshot is uploaded with the timestamp 10:30
* At 11:35 UTC (11:35 local time) gradle dependencies is invoked on
project A. Gradle compares the local timestamp of the last downloaded
artifact (11:05 local time) with the UTC timestamp of the newest
artifact (10:30) in this case. Gradle thinks that it has already
downloaded the latest artifact which is wrong.
Can you confirm this?
Kind regards
Matthias
On 01/26/2012 09:22 AM, Matthias Pfau wrote:
Thank you Luke, that's it.
The following workaround worked for me:
configurations.all {
resolutionStrategy.cacheChangingModulesFor 0, 'seconds'
}
Kind regards
Matthias
On 01/25/2012 10:57 PM, Luke Daley wrote:
On 25 Jan 2012, at 21:55, Matthias Pfau wrote:
Hi there,
with milestone 7 my snapshot dependencies have not been updated a
couple of times when running gradle. However, this only happens
sometimes and I have not found a stable way to reproduce. After
deleting the gradle cache, the updated artifacts are downloaded. I'm
running against a nexus repository.
Has someone else experienced these problems?
You're probably hitting
http://forums.gradle.org/gradle/topics/failure_to_detect_changing_snapshot_dependencies_in_m7_works_in_m6
This has been fixed for the next release.
--
Luke Daley
Principal Engineer, Gradleware
http://gradleware.com
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
