Bug #779 (closed)
Opened 17 years ago
Closed 15 years ago
Dist's "ant update" sometimes fails to update jars
Reported by: | jamoore | Owned by: | jamoore |
---|---|---|---|
Priority: | minor | Cc: | |
Sprint: | n.a. | ||
Total Remaining Time: | n.a. |
Description
Assuming one is trying to update etc/local.properties into omero.ear!local.properties, the update is done only when:
- time(etc/local.properties) > time(omero.ear!local.properties)
and time(omero.ear) plays no role. Therefore to ensure that the update occurs on has to touch etc/local.properties (something of a hack, but there appears to be no other way).
Ref: http://issues.apache.org/bugzilla/show_bug.cgi?id=10755
Note: this arose when a user had moved omero.ear to a system with a different timezone. The jar was silently NOT updated, causing issues.
Change History (3)
comment:1 Changed 17 years ago by jmoore
- Owner changed from callan to jmoore
- Status changed from new to assigned
comment:2 Changed 16 years ago by jmoore
- Milestone changed from 3.0-Beta3 to 3.0-Beta4
comment:3 Changed 15 years ago by jmoore
- Resolution set to fixed
- Status changed from assigned to closed
With the changes for #800, ant update has been removed.
r1781 attempted to fix this but the update target should still be considered broken when timestamps are involved (for example):
Then a user in an earlier timezone:
The only workaround may be to use shell scripts.