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

Bug 290914

Summary:	should we retag 3.5.2 bundles so all bundles include TSA support?
Product:	[Eclipse Project] Platform	Reporter:	Kim Moir <kim.moir>
Component:	Releng	Assignee:	Kim Moir <kim.moir>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	beckyang, daniel_megert, tjwatson
Version:	3.6
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Kim Moir

2009-09-30 10:08:16 EDT

The way that the build works is that we compile the jars, sign them, and then   compare the newly built jars against a baseline composite repository of previous builds.  Thus the unless a bundle changes its qualifier, the older bundle with the same qualifier will be used.  Given that the eclipse.org signing process now includes TSA support, the only way to ensure that all the 3.5.2 bundles include the new TSA support (bug 263708) is to increment their versions.  This will avoid problems such as those described in bug 290668.

Comment 1 Kim Moir

2009-09-30 10:10:54 EDT

*** Bug 290668 has been marked as a duplicate of this bug. ***

Comment 2 Kim Moir

2009-09-30 10:11:48 EDT

Tom, I'm not sure if this needs to be raised at the arch call.

Comment 3 Thomas Watson

2009-09-30 10:23:22 EDT

Yes we need to bring this up in the arch call.  In light of the executable feature version issue (bug 290653) we need to be very careful that all our features get their versions incremented.  Even the ones not included in the Eclipse SDK.

Comment 4 Kim Moir

2009-09-30 11:48:06 EDT

The decision reached in the arch call was
-Not to retag 3.5.2 bundles
-There's a workaround to the exception described here
https://bugs.eclipse.org/bugs/show_bug.cgi?id=290668#c2
-Ensure that all 3.6 bundles are tagged so they include TSA support