A target definition is a set of features and plug-ins that will be used to build plug-in and feature projects against. The target definition is an XML file that is typically persisted in a project or top-level container that can be shared in a source code repository for other developers to use.
com.packtpub.e4.target.mars
.target
:com.packtpub.e4.target.mars
project to store the target definition, and call it com.packtpub.e4.target.mars
. This will allow anyone building the project to use that target platform to build the project. Select the Base RCP (Binary Only) template:com.packtpub.e4.target.mars.target
file and the target definition editor will be shown:javax.inject
.Eclipse Mars
and click on Add to add new content.A target platform was created, consisting of the basic RCP features and plug-ins, using both E4 and Eclipse 3.x functionality. The content is based on the running platform, which means that when run in different versions of Eclipse, different versions will be used.
Some of the code created in the earlier chapters uses Eclipse 3.x technology; for example, bundles that depend on org.eclipse.ui
have activators and handlers used by the older platform, and often miss out dependencies on org.eclipse.jface
or org.eclipse.core.runtime
. By removing the org.eclipse.rcp
dependency from the target platform, it becomes possible to see where these dependencies are and to remove or upgrade them.
18.116.50.87