On 26/01/2012, at 10:40 AM, Matthias Pfau <p...@l3s.de> wrote: > 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?
Would you be able to raise this as a problem at http://forums.gradle.org? Thanks in advance. It's much easier for us to track it as a piece of work that way and to communicate its status. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
