The TableTreeViewer and related classes are now "back in" build 
I20150914-2000 .  For those effected by it's removal, please verify 
quickly all is well when using that 0914-2000 build. I say "quickly" since 
we are producing our Neon M2 build this week (Wednesday) so want to be 
sure nothing was accidentally missed during its restoration. 

As John mentioned, we will leave this in for Neon, but may still want to 
remove it for Neon+1 so comments still welcome in the bug originally 
requested for comments about its removal (bug 434575). 

Thanks, 




From:   David M Williams/Raleigh/IBM@IBMUS
To:     Cross project issues <cross-project-issues-dev@eclipse.org>, 
Date:   09/13/2015 12:57 PM
Subject:        [cross-project-issues-dev] TableTreeViewer removed (please 
comment in bug 434575)
Sent by:        cross-project-issues-dev-boun...@eclipse.org



Thanks for letting us know of the unexpected impact, Ed. I'll talk to the 
team, and coordinate our response. 

For a number of reasons, this may take several days, so in the mean time 
... are there any other projects effected by this? 
You should be able to tell, other than brute force searching for the 
family of classes, by building against our latest I-build, I20150908-0800, 

or using it as a PDE target. If you are effected, please comment in bug 
434575.

Also, in the mean time, for those of you that "migrated" (e.g. Doug/CDT, 
for one) can you briefly write-up what changes were needed? Or, point to 
some Git commits that show the changes? 
I'll confess my ignorance here, but I'm trying to determine if there is an 
"easy pattern" to migrating, or if something that would be highly 
variable? 
Again, a brief comment in bug 434575 would be the best place to put these, 
so easier to find in future. 

Thanks again, and my personal apologies for the churn, 





From:        Ed Merks <ed.me...@gmail.com>
To:        Cross project issues <cross-project-issues-dev@eclipse.org>, 
Date:        09/12/2015 04:06 AM
Subject:        [cross-project-issues-dev] Unannounced Changes Have 
Unforeseen        Consequences
Sent by:        cross-project-issues-dev-boun...@eclipse.org



Hi,

It was brought to my attention that 
org.eclipse.jface.viewers.TableTreeViewer has been deleted.  Yes, I know 
it's deprecated, but nevertheless it was once API before being 
deprecated so deleting it is a breaking change.  I don't recall there 
being an announcement to begin deleting arbitrary deprecated API.

In any case, I can't necessarily commit to making the necessary 
changes.  As such I can't commit to contributing EMF Core to Neon.

I would suggest reconsidering the strategy of breaking APIs and most 
certainly suggest any such actions ought to be announced and discussed 
before such actions are taken.

Regards,
Ed
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe 
from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe 
from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Reply via email to