We rely on date/time-stamps to deploy only the code that has changed to our various environments. While developing a deployment mechanism to deploy from the archived Hudson artifacts for a particular build, we realized that upon archival of the artifacts, Hudson sets the timestamps of all archived files to the present time (when the archiving is taking place). This is preventing us from deploying only the code that has changed.

Shouldn't Hudson preserve the timestamps when it is archiving the artifacts?