Test your Common Navigator Stuff on this Week’s I Builds!

There are changes to the way the Common Navigator selects content extensions for label providers that might be incompatible with existing implementations.  These are in bug 252293 and are available in any I build after I20090125-2000.  So far so good.  I have tested these with JDT, CDT, and the Eclipse SDK (without JDT) and everything seems OK.

We are waiting on a version of WTP with the ICU changes to test with that.

The reason for these changes is that the previous behaviour was non-deterministic (based on the presence of something in a cache), and that in order to fix the above mentioned bug there is a possibility of introducing incompatible behaviour; we wanted to get this into M5 to maximize its exposure.

If you have code that uses the Common Navigator, please test it in the next couple of days (say by Weds 28 Jan) if there is a possibility of incompatibility in the way you use label providers.   See the comments in the above mentioned bug for more details.

If you do have compatibility problems, please immediately open a bug to Platform UI and we will get it addressed this week in 3.5M5, provided we get the bug report by Weds.


About francisu

VP, Architecture at Talend, overall responsible for product architecture and governance. Also maintainer of the Jenkins EC2 plugin.
This entry was posted in Common Navigator. Bookmark the permalink.

2 Responses to Test your Common Navigator Stuff on this Week’s I Builds!

  1. Andreas says:

    Hello Francis,
    has there been any improvements on integrating CN in RCP applications? I experimented some time ago with it (http://www.cpuidle.de/blog/?p=48) and it wasn’t quite easy. Is there a better tutorial for this than the one mentioned?

  2. Francis Upton says:

    There is documentation for how to use the CNF in the RCP case now in the Platform Plugin Developer’s guide, under “Common Navigator Framework”, and this has all of the instructions you need. For 3.5 I’m planning on dealing with the issue of making setting the input a bit easier, but other than that, I think it’s not too difficult at this point. I invite you to try again, and if you find difficulties to make comments or file bugs on them so they can be addressed.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s