Start line:  
End line:  

Snippet Preview

Snippet HTML Code

Stack Overflow Questions
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
<html lang="en">
<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>Plug-ins Tab</title>
<link href="../../book.css" rel="stylesheet" type="text/css">

<h1>Plug-ins Tab</h1>
<p>When testing your plug-in, you have the ability to manage and select the list of plug-ins that you want to launch with on the  <strong>Plug-ins Tab</strong> of the launch configuration. </p>
<p><img src="../../images/launchers/launcher_eclipse_plugins.png" alt="Plug-ins tab" ></p>

<h2>Launch Options </h2>
<p>The <strong>Launch with</strong> combo box allows you to configure the way the Eclipse Application is launched. The options are explained in more detail below.</p>
<p>The <strong>all workspace and enabled external plug-ins</strong> option is the default setting. With this option, the runtime Eclipse application you are launching will be made up of all the workspace plug-ins and all the plug-ins that are explicitly checked on the <strong>Window &gt; Preferences... &gt; Plug-in Development &gt; Target Platform</strong> preference page. This option requires little maintenance because the list of plug-ins is maintained by PDE and updated prior to every launch as plug-ins are created or deleted in the workspace. This option is recommended when the <strong>Program to Run</strong> setting on the <a href="eclipse_main.htm">Main tab</a> of the launch configuration is set to the <strong>default product</strong> or <strong>default application</strong> of your target. </p>
<p>The <strong>plug-ins selected below only</strong> option is typically used when you are testing an RCP application that uses a subset of the plug-ins from the workspace and target. This setting requires more maintenance than the other options, since you have to ensure that the list of selected plug-ins is up-to-date when you add or remove a plug-in from the workspace. <strong>Add Required Plug-ins</strong> should be used to ensure the subset of plug-ins you have selected is complete.</p>
<p>The <strong>features selected below</strong> option can be used to launch an RCP application by specifying features. It also allows to specify the location from where the feature plug-ins should be picked - Workspace or External (Target Platform). The plug-in resolution is first find location. Thus, if a plug-in marked for Workspace is not found there, then it is searched in External location and vice-versa. Select <strong>Add Plug-ins...</strong> to add individual plug-ins to the launch configuration. <strong>Select Required</strong> will look for the dependent features of the presently selected features and add them also to the configuration. If there are many features, <strong>Select Features...</strong> can be used to find and select specific features.</p>
<p>Feature-based configurations launch with plug-ins resolved from the selected features and any additional plug-ins <em>as well as </em> all required plug-ins.  This means that a minimal set of features/plug-ins can be selected and still have a valid launch.</p>
<p><img src="../../images/launchers/launcher_eclipse_features.png" alt="Plug-ins tab" ></p>
<p>Please note that if a workspace plug-in has the same ID as a target plug-in, the workspace plug-in is used in place of its target counterpart. This behavior applies to all three plug-in selection options described above; however, you can override this option by choosing the third option, deselecting a workspace plug-in and selecting the target plug-in with the same ID. </p>

<h2>Validate Plug-ins</h2>
<p>Selecting <strong>Validate Plug-ins</strong> analyzes the selected set of plug-ins to find launching startup problems. For instance, missing dependencies, unsatisfied execution environments, incompatible platform filters are a few of the potential problems that may prevent your plug-in from running.</p>
<p>By checking the <strong>Validate plug-ins automatically prior to launching</strong> option, PDE will run the <strong>Validate Plug-ins</strong> function prior to every launch. If problems are found, an error dialog will appear for you to examine and you can choose to either continue the launch without correcting the problems or cancel the launch to rectify the issues. Otherwise, if no problems are found, the launch proceeds as normal. </p>

<p><img src="../../../images/ngrelr.png" alt="Related reference"></p>
  <a href="eclipse_application_launcher.htm">Eclipse Application Launcher</a><br>
  <a href="junit_launcher.htm">JUnit Plug-in Test Launcher</a><br>
  <a href="equinox_launcher.htm">OSGi Framework Launcher</a><br>
  <a href="junit_test.htm">Junit Launcher Test Tab</a><br>
  <a href="eclipse_main.htm">Main Tab</a><br>
  <a href="arguments.htm">Arguments Tab</a><br>
  <a href="plugins.htm">Plug-ins Tab</a><br>
  <a href="configuration.htm">Configuration Tab</a><br>
  <a href="tracing.htm">Tracing Tab</a><br>
  <a href="environment.htm">Environment Tab</a><br>
  <a href="common.htm">Common Tab</a>

New to GrepCode? Check out our FAQ X