blob: 6e13d34280b0ea5027cd1ee3c6ee595f42732cb1 [file] [log] [blame]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//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>Inspecting the current configuration</title>
<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>Inspecting the current configuration</H1>
<p>The
<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.help.aboutAction")'>
<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
<b>Help &gt; About Eclipse SDK</b></a>
dialog shows most of the important information about the features and plug-in configured in
the product. To find out further detailed information about the current configuration:
</p>
<ol>
<li>Open the update configuration manager by clicking
<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.update.manageConfiguration")'>
<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
<b>Help &gt; Software Updates &gt; Manage Configuration</b></a>.
This opens the Product Configuration dialog.</li>
<li>In the Product Configuration dialog expand the root node (current&nbsp;
configuration).
The first tier of items are locations on the local computer where the files
for features and plug-ins are stored. For a typical product, all features
are installed in a single directory sub-tree. However, a feature that is
installed as an extension of another product are usually located in a
separate directory sub-tree.</li>
<li>Expand the location to see the feature versions installed there.</li>
<li>The nesting of the features indicates which child features are included in
a given parent feature. Nested features act as a unit.</li>
<li>Select a feature version and click <b>Show Properties</b> to open the
Properties dialog which presents more detailed information about the selected feature.</li>
<li>Click <b>Show Disabled Features</b> filter on the toolbar of the Product
Configuration dialog. Any feature versions that are disabled are now
shown (you might not have any). Disabled feature versions are ones that are
installed on the local computer but excluded from the current configuration.
At most one version of any given feature can be present in a given
configuration; usually the ones with the lower version numbers will be in a
disabled state.</li>
<li>In the Properties dialog of a feature, click <b>Status</b> to find out whether
the selected feature is configured exactly as packaged. The status will show
when a feature's plug-ins are present at different versions, or disabled due
to missing prerequisite plug-ins that are expected to be supplied by some
other feature.</li>
</ol>
<p>
In this dialog you can revert to a previous install configuration, view the installation history, or
even add another eclipse product extension. A product extension is a local folder that has a similar
file layout as the eclipse installation, but with a .eclipseextension marker (instead of .eclipseproduct).
If you add a product extension, make sure there are no duplicate features in the extension
you add.
</p>
<p>
When the install wizard is used to install features in a user selected location, that location
automatically becomes an eclipse product extension.
</p>
<P><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
<a href="../concepts/concepts-25.htm">Features</a>
</P>
<P><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
<a href="tasks-34.htm">Installing new features with the update manager</a><br>
<a href="tasks-36.htm">Updating features with the update manager</a><br>
<a href="tasks-37.htm">Update Policy</a>
</p>
</BODY>
</HTML>