Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Heads up : TCF rename for 1.0 version



David reminded me that a Bug is a better channel for feedback, so questions and comments there please:





From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Oberhuber, Martin
Sent: Wednesday, May 02, 2012 6:37 PM
To: Cross project issues (cross-project-issues-dev@xxxxxxxxxxx)
Subject: [cross-project-issues-dev] Heads up : TCF rename for 1.0 version


Hi all,


If you have any bundles which depend on TCF, please read on – if not, feel free to ignore.


Earlier this year the TCF project performed a refactoring of its namespace in order

to better comply with Eclipse naming after its separation from the TM project [1].


The change has now matured, and we consider TCF-1.0 the latest, greatest and most

stable version which we’ll want to hit the Simulataneous Release.

Bundle ID’s, Java packages and extension point identifiers change as follows :


-          TCF 0.5 Stream (up until Juno M6) :

-          TCF 1.0 Stream (Juno M7 and on) : org.eclipse.tcf


A preview of the TCF M7 contribution (with TCF 1.0) is available here:

and should be on the Simultaneous Release Staging repo shortly.


I believe that the older tcf-0.5 builds will also be available from the

Simultaneous repo due to still exposing M6 and older milestone repos,

but we encourage all adopters upgrade to the 1.0 version since 0.5

is not maintained any more.


Your work for adopting 1.0 should simply be a textual “search and replace”

As per above.


Let me know if there are any questions or concerns.







Martin Oberhuber, SMTS / Product Architect – Development Tools, Wind River

direct +43.662.457915.85  fax +43.662.457915.6


Back to the top