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>Settings Tab</title>
<link href="../../book.css" rel="stylesheet" type="text/css">

<h1>Settings Tab</h1>
<p>The <strong>Setting Tab</strong> allows you to customize the Java Runtime Environment (JRE) and configuration area settings of the launch configuration. </p>
<h1><img src="../../images/launchers/launcher_equinox_settings.png" alt="Equinox Settings" > </h1>

<h2>Java Executable</h2>
<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>

<h2>Java Runtime Environment</h2>
<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 &gt; Preferences.... &gt; Java &gt; 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>

<h2>Bootstrap Entries</h2>
<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 &gt; Preferences... &gt; Plug-in Development &gt; 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>

<h2>Configuration Area</h2>
<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><img src="../../../images/ngrelr.png" alt="Related reference"></p>
  <a href="equinox_launcher.htm">OSGi Framework Launcher</a><br>
  <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_plugins.htm">Bundles Tab</a><br>
  <a href="equinox_args.htm">Arguments Tab</a><br>
  <a href="equinox_settings.htm">Settings 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