Yes, after thinking about it for a while, I decided that that must be what was going on. Quite a good idea really... Although in company projects that are only used in one timezone, I imagine there will be resistance from developers (e.g. mine :( )
It was funny - I am from New Zealand, and we are +12 GMT, so it looked like it was AM/PM issue! :) Hervé BOUTEMY wrote: > > Le vendredi 3 août 2007, Antony Stubbs a écrit : >> My deploy goal generates files with timestamps on them, like so: >> >> ETRWebEAR-1.0.2-20070803.083222-6.ear >> >> however, when i created this - the time was 8:32 PM! not AM, as the '24 >> hour' timestamp implies. >> The clock on my sys try correctly says ~8:30 pm. >> >> I could not find any posts on the topic, and i haven't waited 12 hours to >> see if it's only a '12 hour' timestamp, and not 24 hour, but i doubt >> that. >> >> Has anyone encountered this? Shall I file a bug report? > > AFAIK, the timestamp in the filename is expressed as UTC, not local time: > this > permits people all around the planet to work on the same artifact without > having conflicts. > > regards, > > Hervé > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Incorrect-timestamp-of-deploy-artifact---12-hours-out--AM-vs-PM-tf4211367s177.html#a12002008 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
