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

Bug 265320

Summary: [CommonNavigator] Breaking change causes adopters of WorkingSetsContentProvider to fail
Product: [Eclipse Project] Platform Reporter: Chuck Bridgham <cbridgha>
Component: UIAssignee: Francis Upton IV <francisu>
Status: RESOLVED DUPLICATE QA Contact:
Severity: major    
Priority: P3 CC: francisu
Version: 3.5   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Chuck Bridgham CLA 2009-02-18 11:11:48 EST 
The change in question is to the Resource WorkingSetsContentProvider from bug 189490 - which has a public id (API) - making it valid to bind to any Common Navigator instance.

This change has introduced a reference to the "Project Explorer", which is the main adopter, but not the only adopter of this content binding.


We are now getting class casts thrown like the following:

ava.lang.ClassCastException: com.ibm.etools.ui.navigator.SDNavigator incompatible with org.eclipse.ui.navigator.resources.ProjectExplorer
        at org.eclipse.ui.internal.navigator.workingsets.WorkingSetsContentProvider.init(WorkingSetsContentProvider.java:78)
        at org.eclipse.ui.internal.navigator.extensions.SafeDelegateTreeContentProvider.init(SafeDelegateTreeContentProvider.java:159)
        at org.eclipse.ui.internal.navigator.extensions.NavigatorContentExtension.internalGetContentProvider(NavigatorContentExtension.java:139)
        at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.getParent(NavigatorContentServiceContentProvider.java:473) 

Can we make these contributions compatible again for all common navigator instances in M6? - meaning can we add similar function (getRootMode(),setRootMode()) to Common Navigator?
Comment 1 Francis Upton IV CLA 2009-02-18 11:18:31 EST 
Yes, I will take care of this for M6.  Sorry about the trouble.

See also bug 265049.
Comment 2 Francis Upton IV CLA 2009-03-05 17:14:50 EST 

*** This bug has been marked as a duplicate of bug 265049 ***