Has anyone come across issues with timestamps when jar'ing (war) up apps
?
We've just hit an issue where an app is built in one region which ends
up with timestamps with zone set to GMT and is about to be used GMT+5 -
Tomcat thinks all the classes are old and continually reloads things -
there are options for getting Tomcat to ignore timestamps, but I'd
rather work this out on the build side. Anyone have experience with this
sort of thing - also seems that it depends on which version of jar you
use - eg Sun JDK 1.3 jar seems to not record timezones whereas 1.4 does.
Thanks
Bernard
--------------------------------------------------------

NOTICE: If received in error, please destroy and notify sender.  Sender does 
not waive confidentiality or privilege, and use is prohibited.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to