Installation procedure always installs two JPOs after the daylight saving time changed

jlabbe-processia / mxupdate

Automatically exported from code.google.com/p/mxupdate

1 stars 1 forks source link

Installation procedure always installs two JPOs after the daylight saving time changed #82

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago

The two JPOs org.mxupdate.install.Insert and org.mxupdate.util.JPOHandler are 
always installed 
with the files are in different daylight saving time zones.

This happens because of the different handling of the last modification time 
between TCL and Java.

Original issue reported on code.google.com by tim.mox...@googlemail.com on 29 Oct 2009 at 2:03

GoogleCodeExporter commented 8 years ago

solved with r597

The tcl routine to check if a JPO must be installed ignores now +/- 1 hour.

Original comment by tim.mox...@googlemail.com on 29 Oct 2009 at 2:06

Changed state: Fixed
Added labels: Version-0.7.2

GoogleCodeExporter commented 8 years ago

Original comment by tim.mox...@googlemail.com on 1 Nov 2009 at 4:15

Changed title: Installation procedure always installs two JPOs after the daylight saving time changed

GoogleCodeExporter commented 8 years ago

released

Original comment by tim.mox...@googlemail.com on 2 Nov 2009 at 1:34

Changed state: Done

GoogleCodeExporter commented 8 years ago

Original comment by tim.mox...@innobix.com on 7 Feb 2014 at 8:27

Added labels: Status-Done

GoogleCodeExporter commented 8 years ago

Original comment by tim.mox...@innobix.com on 7 Feb 2014 at 8:28

Added labels: MigrationStatus-Done