Multiple versions of the same bundle during the build

Following the theme "pde to support multiple versions", I've just released the support for multiple versions in PDE Build.
This means that you can now build a product / feature made of multiple versions of the same bundle (given that they are not marked singleton).

How do you do that:
- In the feature.xml, identify the plugin and replace the 0.0.0 by the first three segments of the desired version followed by the string "qualifier". Example:
    <plugin id="org.junit" version="3.8.1.qualifier" ... />
    <plugin id="org.junit" version="4.1.0.qualifier" ... />

- In the map file, identify the plugin and add the first three segments of the version before the '=' sign (don't forget the comma)
    plugin@junit,3.8.1=v20070301.....
    plugin@junit,4.1.0=v20070301.....

Of course, if you don't use multiple versions you don't have to do anything new.

From visual studio to CDT

An article explaining how to import a simple VS C/C++ project into CDT.

Design patterns for UI

While reading a post from Grady Booch, I came across the yahoo design pattern library which seems to be a very interesting concept that could be adopted by the user interface best practices working group to publish their results.

Being rich

No, I'm not commenting about my lifestyle <g>, I'm just talking about RCP, the Really Cool Platform. Lately I've been annoyed by this tendancy to call anything built on top of eclipse, an RCP application. This is just wrong as it creates confusion around a concept not easy to understand, and it does not promote SWT and/or JFace where they are the real "heros".

So what does it take to be rich? To depend on org.eclipse.ui and org.eclipse.core.runtime (see the wiki).

Now remember that and give credit to the right technology even though it may not market as well (sorry azureus is not rich, it is SWeeT).