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

Bug 392910

Summary:	Change build qualifier generation in RAP Runtime and Tools build
Product:	[RT] RAP	Reporter:	Markus Knauer <mknauer>
Component:	Releng	Assignee:	Project Inbox <rap-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3
Version:	2.0
Target Milestone:	2.0 M3
Hardware:	PC
OS:	Linux
Whiteboard:

Description Markus Knauer

2012-10-26 08:11:11 EDT

Up to now we generate a new version qualifier with every new build based on the timestamp when the build had been started. The result of this approach is that we create new bundle and feature versions even if nothing has changed.

With the release of Tycho 0.16 the possibilities have changed. It is now possible to generate qualifiers based on the last modification time (bundles) and last direct dependency modification (features). We are already using this in the RAP incubator builds and tested this extensively with the Tycho 0.16.0-SNAPSHOT versions.

If we introduce this *now*, I would suggest that we (manually) ensure that at least one file changed in all bundles within the last couple of days. That way we circumvent possible problems with bundles that haven't changed recently and that are included with a higher version qualifier in the first Kepler milestones.

Comment 1 Markus Knauer

2012-10-26 11:55:01 EDT

Implemented for RAP Runtime with commit 2904cba2a0a31af3fa5c0c981484ee5d7789ef67

Comment 2 Markus Knauer

2012-10-26 12:09:48 EDT

Implemented in RAP Tools with commit d9a80252f0ba72af633e0e70a2bb3e2b779e7dff

Comment 3 Markus Knauer

2012-10-31 06:54:16 EDT

(In reply to comment #0)
> If we introduce this *now*, I would suggest that we (manually) ensure that
> at least one file changed in all bundles within the last couple of days.
> That way we circumvent possible problems with bundles that haven't changed
> recently and that are included with a higher version qualifier in the first
> Kepler milestones.

With the new version qualifier algorithm it happens now that we generate version qualifiers that are *less* than the ones we created before. This leads to problems in all cases where users try to install the 'latest' version. I see two potential solutions to this problem: Either remove all existing RAP 2.0 releases from all p2 repositories (in my opinion we should not go this way), or manually commit a 'dummy' change to all projects to ensure that they use the actual date/time as minimum timestamp in the version qualifier.

Ccommit b0e2524888daa85a90246e1156ef18c02f03f7d5 (RAP Runtime) and commit a54c811cf405b4ab0e51e5f2e1e2d20186f8e1eb (RAP Tools) contain such a dummy commit that adds a whitespace/blank to all .project files.

Comment 4 Markus Knauer

2012-12-05 05:24:10 EST

We were using dummy changes in order to ensure that we start with a good enough base qualifier. All future qualifiers will have a higher number. Closing this bug now - it had been implemented with RAP 2.0 M3.