| <!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"> |
| <title>Settings Tab</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">Settings Tab</p> |
| <p>The <strong>Setting Tab</strong> allows you to customize the Java Runtime Environment (JRE) and configuration area settings of the launch configuration. </p> |
| <p class="style1"><img src="../../images/launchers/launcher_equinox_settings.png" alt="Equinox Settings" hspace="30"> </p> |
| <p class="style1"> </p> |
| <p class="style2">Java Executable</p> |
| <p>The <STRONG>Java Executable</STRONG> option allows you to specify the executable to run the <em>Equinox OSGi Framework</em> with. For example, on <em>Windows</em> you can override the default executable, <em>javaw.exe</em>, with <em>java.exe</em> if desired.</p> |
| <p> </p> |
| <p class="style2">Java Runtime Environment</p> |
| <p>You can test your bundle against the Java Runtime Environment (JRE) of your choice; furthermore, this runtime JRE does not necessarily have to be the same JRE (with associated SDK) utilized to compile the workspace bundles. </p> |
| <p>The <STRONG>Runtime JRE</STRONG> combo box is populated with all the JREs listed on the <STRONG>Windows > Preferences.... > Java > Installed JREs</STRONG> preference page. You can dynamically add more JREs to the list of installed JREs by pressing the <STRONG>Installed JREs...</STRONG> button, which will open the <STRONG>Installed JREs</STRONG> preference page. </p> |
| <p> </p> |
| <p class="style2">Bootstrap Entries</p> |
| <p>By default, the only entry on the launch configuration classpath is the <em>${target_home}/plugins/org.eclipse.equinox.launcher</em> JAR. The <em>${target_home}/plugins/org.eclipse.equinox.launcher</em> JAR file houses the <em>org.eclipse.equinox.launcher.Main</em> class which contains the bootstrap code. The <em>${target_home}</em> variable refers to the location of the target platform as specified on the <strong>Window > Preferences... > Plug-in Development > Target Platform</strong> preference page. </p> |
| <p> The <STRONG>Bootstrap Entries</STRONG> field allows you to specify and append additional locations to the classpath, if required.</p> |
| <p> </p> |
| <p class="style2">Configuration Area</p> |
| <p>Every <em>Equinox OSGi Framework</em> instance has a unique configuration area which contains metadata, caches and configuration files read by the framework and possibly other bundles. </p> |
| <p>Typically, the location of the configuration is not important; therefore, PDE generates a unique configuration area for every launch in its own metadata area. This configuration area is deleted when the launch configuration is deleted.</p> |
| <p>If desired, the user can set the location of the configuration area. Variables in the directory path are supported in order to facilitate shareable launch configurations among team members.</p> |
| <p>You also have the option to <strong>Clear the configuration area before launching</strong>, which is useful for testing how bundles cache data in that area. </p> |
| <p> </p> |
| <p class="style1"> </p> |
| </body> |
| </html> |
