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, 2012. 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">
<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/"></script>
<title>Plug-in Content</title>
<link href="../../book.css" rel="stylesheet" type="text/css">

<h1>Plug-in Content</h1>
<p>The <strong>Plug-in Content</strong> wizard page allows you to customize the plug-in data. </p>
<p><img src="../../images/new_wizards/plugin_content.PNG" alt="Plug-in Content" ></p>

<h2>Plug-in Properties </h2>
<p>A <strong>ID</strong> is mandatory and must comply with the   <a href="../../../../org.eclipse.platform.doc.isv/reference/misc/plugin_manifest.html">plugin.dtd</a>. It is recommended - but not mandatory - for the plug-in ID to match the plug-in project name.</p>
<p>A <strong>Version</strong> is mandatory and must be of the form <em>major.minor.micro.qualifier</em> (e.g. 1.3.0).</p>
<p>A <strong>Name</strong> is the translatable presentation name of the plug-in. This field is required. </p>
<p>A <strong>Vendor</strong> is the translatable name of the plug-in vendor. This field is optional. </p>
<p><strong>Execution Environment</strong> refers to the required <a href="">execution environment</a> (symbolic representation of a JRE) of your plug-in. This field is optional but recommended to be set.</p>

<h2>Plug-in Options </h2>
<p>An <strong>activator</strong> is a Java class that controls the plug-in's life cycle. It is only needed if you require to do work upon the startup or shutdown of your plug-in. </p>
<p>The choice of whether the plug-in will make contributions to the UI affects the code generated for the activator:</p>
  <li> If the plug-in is a UI plug-in, the activator class extends the <em>org.eclipse.ui.plugin.AbstractUIPlugin</em> class. </li>
  <li>If the plug-in is headless (i.e. non-UI), the activator extends the <em>org.eclipse.core.runtime.Plugin </em>class. </li>
  <li>If the plug-in is targeted for an OSGi framework, the activator implements the <em>org.osgi.framework.BundleActivator</em> interface. </li>
<p>The choice of a UI vs. headless plug-in also controls what templates are available on the <a href="plugin_templates.htm">next wizard page</a>. </p>
<p>Adding <strong>API Analysis</strong> to the project will enable static analysis of API usage from the new project.</p>

<h2>Rich Client Application</h2>
<p>At a minimum, a rich client application requires a plug-in with an <em>org.eclipse.core.runtime.applications</em> extension. If branding is desired, an <em>org.eclipse.core.runtime.products</em> extension is required. By answering <strong>Yes</strong> to the question in the <strong>Rich Client Application</strong> section, you will be required to go to the <a href="plugin_templates.htm">Templates</a> page where you can choose an RCP template that will generate all the required extensions.</p>
New to GrepCode? Check out our FAQ X