Building the e4 tools locally with CBI

In case you are building Eclipse4 RCP applications (which you should Eclipse 3.x RCP is just legacy these days), you may want to use the latest and greatest version of your e4 tooling.

I updated the description how to build the e4 tools locally you can find it here:

Local build of the e4 tools

You should really try this. The additional update of building the e4 tools locally, is that you can now fix issue here youself, test them locally and provide patches.

About Lars Vogel

Lars Vogel is the founder and CEO of the vogella GmbH and works as Eclipse and Android consultant, trainer and book author. He is a regular speaker at international conferences, He is the primary author of With more than one million visitors per month this website is one of the central sources for Java, Eclipse and Android programming information.
This entry was posted in Eclipse and tagged . Bookmark the permalink.

2 Responses to Building the e4 tools locally with CBI

  1. Scott Anderson says:

    3.x RCP isn’t legacy if you use any workbench components… those are emulated and quite slow. The impression I got at JavaOne was that those are not going to be ported to 4.x any time soon. Is this incorrect?

  2. Lars Vogel says:

    @Scott: it is still legacy, even if you use other legacy stuff. 🙂 To answer your question: yes, we we are planning to migrate certain parts to a pure Eclipse 4 environment. You are welcome to help in this effort.

Comments are closed.