blob: 566f859505aac6410795e678a8a19a393f7f8c05 [file] [log] [blame]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><HTML>
<HEAD>
<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. 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">
<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
<title>Converting projects into PDE projects</title>
</head>
<BODY BGCOLOR="#ffffff">
<h1>Converting existing projects into PDE projects</h1>
<p>A PDE project is a project that &quot;knows&quot; it hosts a plug-in and is
eligible for plug-in-specific operations. </p>
<p>PDE is fully capable of working on plug-ins in the workspace represented as
ordinary projects. However, it cannot offer incremental file checking,
capability-based filtering and other similar features if a project does not
possess full PDE capabilities.</p>
<p>It is
possible to convert a regular project into a PDE project at any point. For
example, you may have some Java classes that you want to package into a library
and share with others as a plug-in. Alternatively, you may want to get full
support for manifest syntax checking and reporting that only PDE projects have.</p>
<p>To convert projects into PDE projects, select a project in the Navigator view.
Select <b>PDE Tools &gt; Convert Projects to Plug-in Projects...</b> from the
context menu.</p>
<p align="center">
<img border="0" src="images/convert-java.png" alt="&quot;Convert Existing Projects&quot; wizard" ></p>
<p>The wizard will list all projects that do not have PDE capability.
Candidate projects do not need to have manifest files. If they are missing, PDE
will create generic ones you can use as a starting point. Files that already
exist will be left intact. Select one or more projects, click <b>Finish</b>.</p>
</body>
</html>