View source for FAQ Can I install plug-ins outside the main install directory?

Users who like to &#147;live on the edge&#148; will be frequently installing new builds of Eclipse. When a new build is installed,  a manual step is generally required to copy over any extra plug-ins from the old build to the new one.  We all know how much programmers hate manual steps, so it would be nice if there were an easy way to link a set of external plug-ins into  Eclipse builds.  A mechanism to do that is called a <i>product extension</i>.

A product extension must be laid out on disk in a certain way so the Eclipse configuration tools can recognize it.  Following is the disk layout for a product extension that contains a single plug-in called  <tt>org.eclipse.faq.examples</tt>.

<pre>
   eclipse/
      .eclipseextension
      plugins/
         org.eclipse.faq.examples/
            plugin.xml
            examples.jar
         ... optionally more plug-in directories ...
      features/
         ... features would go here ...
</pre>

The file <tt>.eclipseextension</tt> is empty, acting as a special marker that tells install tools that this is an Eclipse extension.  Other than 
that special file, the layout is the same as that for an Eclipse product. Plug-ins go in a directory called <tt>plugins</tt>, and if the extension contains features, they go in a sibling directory called <tt>features</tt>.

Once you&#146;ve got this directory structure set up, you have to link the product extension into your plug-in configuration.  In Eclipse 3.0, you simply go to '''Help &gt; Software Updates &gt; Manage Configuration''',  choose the option called '''Add an Extension Location''', and select the extension directory when prompted.  That&#146;s all there is to it!  As long as you keep the same workspace when you upgrade to a new build, the product extensions will automatically be available in the new configuration.


== See Also: ==

[[FAQ_How_do_I_upgrade_Eclipse%3F]]

[[FAQ_How_do_I_remove_a_plug-in%3F]]

{{Template:FAQ_Tagline}}