Copyright © 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014 Lars Vogel
Table of Contents
During development of your Eclipse plug-ins, you use other plug-ins for example the SWT and JFace plug-ins.
The set of plug-ins which you can use for your development is defined by the plug-ins in your workspace in addition with the plug-ins defined by your target platform.
By default your Eclipse IDE installation is used as target platform
You can specify your target platform with a target definition file. With such a file you define the available plug-ins and features.
A target platform can be defined based on software sites (p2 update sites) or other means. As the new build system like Maven Tycho support only p2 update sites, it is recommended to use only these.
A target definition file is typically shared between the developers to ensure that everyone is using the same basis for development.
Developing against your IDE installation has the following disadvantages:
it makes you dependent on your version of the Eclipse IDE
it can lead to problems if developers are using different versions of Eclipse because the API might be different
it makes it difficult to upgrade the set of available plug-ins for every developer at the same time
it also requires that you install every plug-in required for your product either in your workspace or in your Eclipse IDE
it can happen that you might unintentionally add plug-ins from the Eclipse IDE to your development
To solve these problems, it is recommended to configure a target platform explicitly via a target definition file.
A target definition file can be created via→ → → → .
You can add new locations via the Software Site and specify the URL.button in the location section. To add an Eclipse p2 update site, select
After you created your target definition file, you can set it as the target platform in your Eclipse IDE via thelink in the Target definition editor as depicted in the following screenshot.
You can switch the target platform in the Eclipse Preferences. Select→ → → .
The most effective way of defining your target platform is to use p2 update sites. These are of the same type as the update sites that you use to install a new set of plug-ins. If the content in the update sites defined by your target platform changes, your local set of plug-ins can be updated.
It is also possible to define your target platform based on plug-ins in your file system, but this is not recommended as certain build system like Maven/Tycho do not support file based target definition files.
Create a new project called com.example.e4.rcp.todo.target of type General.
Create a new target definition file via the→ → → → menu path.
Press the Add... button.
Select Software site in the following dialog.
Press the Group by Category flag.button and enter the http://download.eclipse.org/eclipse/updates/4.3 URL. This is the update site for the Eclipse 4.3 (Kepler) release. Include the Eclipse RCP SDK entry from the Kepler update site. You may have to remove the
Include the Equinox p2 SDK from the Kepler update site.
If you use SWTBot for unit tests, add SWTBot for SWT Testing features from http://download.eclipse.org/technology/swtbot/releases/latest/ to your target platform.
The result should look similar to the following screenshot. Please note that your version numbers might be different.
Afterwards press the Set as Target Platform to activate it. See Section 3.4, “Solving potential issues” in case you have problems with your new target platform.
Try to add the
plug-in as dependency to one of your plug-ins. This should not be
Your target platform depends on external update sites and their packaging of plug-ins. Theses update sites might change over time, so you should be able to revert your target platform settings in case you face issues.
You can switch back to your Eclipse IDE as target platform via→ → → .
I hope you enjoyed this tutorial. You find this tutorial and much more information also in the Eclipse 4 RCP book from this author.
This tutorial is Open Content under the CC BY-NC-SA 3.0 DE license. Source code in this tutorial is distributed under the Eclipse Public License. See the vogella License page for details on the terms of reuse.
Writing and updating these tutorials is a lot of work. If this free community service was helpful, you can support the cause by giving a tip as well as reporting typos and factual errors.
Please consider a contribution if this article helped you. It will help to maintain our content and our Open Source activities.
If you find errors in this tutorial, please notify me (see the top of the page). Please note that due to the high volume of feedback I receive, I cannot answer questions to your implementation. Ensure you have read the vogella FAQ as I don't respond to questions already answered there.
vogella Training Android and Eclipse Training from the vogella team
Android Tutorial Introduction to Android Programming
Eclipse RCP Tutorial Create native applications in Java
JUnit Tutorial Test your application
Git Tutorial Put all your files in a distributed version control system