Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 367945 - Investigate use of ${maven.build.timestamp} in BuildQualifierMojo
Summary: Investigate use of ${maven.build.timestamp} in BuildQualifierMojo
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Tycho (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Martin Schreiber CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-05 08:29 EST by Igor Fedorenko CLA
Modified: 2021-04-28 16:54 EDT (History)
12 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Igor Fedorenko CLA 2012-01-05 08:29:06 EST 
BuildQualifierMojo currently maintains its own reactor build timestamp. Although insignificant from performance and amount of code standpoint, this causes confusion when the same reactor build uses both Tycho and standard Maven timestamps and the two disagree. It is also impossible to access Tycho reactor build timestamp as ${property}, when filtering resources, for example.

Unfortunately, Maven timestamp formatter uses current timezone, which will need to be fixed in Maven core before both Maven and Tycho can produce identical build timestamps.
Comment 1 Tobias Oberlies CLA 2012-01-07 05:10:09 EST 
(In reply to comment #0)
> Unfortunately, Maven timestamp formatter uses current timezone, which will need
> to be fixed in Maven core before both Maven and Tycho can produce identical
> build timestamps.
Is there a chance that this is happening any time soon? Unfortunately, I haven't seen any activity on the Maven project lately (seen from a quite remote viewpoint...)
Comment 2 Igor Fedorenko CLA 2012-01-07 05:59:22 EST 
(In reply to comment #1)
> (In reply to comment #0)
> > Unfortunately, Maven timestamp formatter uses current timezone, which will need
> > to be fixed in Maven core before both Maven and Tycho can produce identical
> > build timestamps.
> Is there a chance that this is happening any time soon? Unfortunately, I
> haven't seen any activity on the Maven project lately (seen from a quite remote
> viewpoint...)

Yes, there is a chance. Why?
Comment 3 Tobias Oberlies CLA 2012-01-07 06:07:26 EST 
I was just a bit worried that Maven doesn't move forward any more. Good to hear that this is not the case.
Comment 4 Jan Sievers CLA 2012-02-08 03:16:44 EST 
move all open bugs to post 0.14.0
Comment 5 Gunnar Wagenknecht CLA 2013-07-05 18:53:30 EDT 
Just had the same idea, i.e. wanted to use UTC timestamps. Well, there is at least a Maven bug now that links to this one.

https://jira.codehaus.org/browse/MNG-5452
Comment 6 Jason van Zyl CLA 2014-06-13 10:32:22 EDT 
This has now been fixed on Maven master (Fixed on 2a4d172600a6252da662edb450e9513067d6ef9e) and will be released in the up coming Maven 3.2.2.

https://jira.codehaus.org/browse/MNG-5452
Comment 7 Michael Osipov CLA 2014-06-15 13:08:25 EDT 
I have spun of another issue for that (https://jira.codehaus.org/browse/MNG-5647) just to make sure that the build timestamp is a parsable ISO 8601 string and denotes the UTC time zone.
Comment 8 Nikolas Falco CLA 2016-07-07 05:06:33 EDT 
Any change to fix it?
Comment 9 Eclipse Genie CLA 2016-11-02 08:18:58 EDT 
New Gerrit change created: https://git.eclipse.org/r/84339
Comment 12 Martin Schreiber CLA 2016-11-22 01:18:14 EST 
Now the ${maven.build.timestamp} is returned within the Default Build Timestamp Provider as build timestamp. If you run a build in a mixed reactor (Maven and Tycho projects) now both projects with have the same build qualifier.