| <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" |
| "http://www.w3.org/TR/html4/loose.dtd"> |
| <html> |
| <head> |
| <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> |
| <script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script> |
| <title>Fragment Project Structure</title> |
| <link href="../../book.css" rel="stylesheet" type="text/css"> |
| <style type="text/css"> |
| <!-- |
| .style1 { |
| font-size: 18px; |
| font-weight: bold; |
| } |
| .style2 { |
| font-size: 12pt; |
| font-weight: bold; |
| } |
| --> |
| </style> |
| </head> |
| |
| <body> |
| <p class="style1">Fragment Project Structure</p> |
| <p>The <strong>Project Structure</strong> wizard page allows you to specify the project name, location, settings and target. </p> |
| <p><img src="../../images/new_wizards/fragment1.png" alt="Fragment Structure" hspace="30"></p> |
| <p> </p> |
| <p class="style2">Project Name </p> |
| <p>When choosing a name for the fragment project, the reverse naming domain convention (e.g. com.example.abc) is recommended - but not enforced by PDE.</p> |
| <p> </p> |
| <p class="style2">Project Location </p> |
| <p>The default location for the fragment project is a subdirectory nested inside the workspace location. To change the location, uncheck the <strong>Use default location</strong> checkbox and enter the location of your choice.</p> |
| <p> </p> |
| <p class="style2">Project Settings </p> |
| <p>Whether or not a fragment project should be created as a Java project depends on whether the fragment will contribute code. Fragment projects that contribute code are housed inside a Java project. Other plug-ins, such as documentation plug-ins do not contribute code and can therefore be contained in simple projects.</p> |
| <p> </p> |
| <p class="style2">Eclipse vs. OSGi Framework </p> |
| <p>The <strong>Eclipse</strong> vs. <strong>OSGi framework</strong> choice acts as pre-filter to determine what initial pages will be visible in the plug-in manifest editor when it opens.</p> |
| <p>Since the extension registry is Eclipse-specific content, the <strong>Extensions</strong> and <strong>Extension Points</strong> pages of the manifest editor are visible only when the <strong>Eclipse version</strong> option is chosen. </p> |
| <p> </p> |
| <p class="style2">Equinox vs. Standard</p> |
| <p>When targeting an OSGi framework, you have a choice between the <strong>Equinox</strong> and <strong>standard</strong> frameworks. The Equinox OSGi framework augments the <em>MANIFEST.MF</em> content with Eclipse-specific headers (e.g. <strong>Eclipse-LazyStart</strong>) and directives (e.g. <strong>x-friends</strong>). If you do not wish to use these Eclipse-specific headers and attributes, then choose the <strong>standard</strong> option. </p> |
| <p> </p> |
| <p> </p> |
| </body> |
| |
| </html> |
