Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 431524

Summary: Tycho Build generates a build timestamp four hours in the future
Product: [ECD] Orion Reporter: Anthony Hunter <ahunter.eclipse>
Component: RelengAssignee: Anthony Hunter <ahunter.eclipse>
Status: RESOLVED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: adrian.aichner
Version: 6.0   
Target Milestone: 6.0 M1   
Hardware: PC   
OS: Linux   
Whiteboard:

Description Anthony Hunter CLA 2014-03-28 14:08:07 EDT 
A Tycho build is started on Mar 28, 2014 1:12:29 PM
The Build timestamp is four hours in the future as I20140328-1714
Comment 1 Adrian Aichner CLA 2014-04-06 17:14:27 EDT 
Could that be an issue of UTC vs. EDT?

A time without a timezone name or offset or a Z or UTC marker is meaningless anyway in a global context.
Comment 2 Anthony Hunter CLA 2014-04-07 16:05:53 EDT 
Tycho uses UTC timezone to calculate the build qualifier. This was a change made in Bug 352838. 

I checked the source:

http://git.eclipse.org/c/tycho/org.eclipse.tycho.git/tree/tycho-packaging-plugin/src/main/java/org/eclipse/tycho/buildversion/BuildQualifierMojo.java

has hard coded:
format.setTimeZone(TimeZone.getTimeZone("UTC"));
on line 136.

So out of the box the our build timestamps are UTC.
Comment 3 Adrian Aichner CLA 2014-04-07 17:27:29 EDT 
Why not use ISO8601 format, e.g. 20140328Z1714, which leaves no room for ambiguity about the time interpretation.

Just a thought.