Difference between revisions of "Equinox p2 Migration Guide"

From Eclipsepedia

Jump to: navigation, search
m (See Also: test cases link)
m
Line 71: Line 71:
  
 
To import such a folder, use <code>Help > Software Updates... > Available Features > Manage sites... > Add... > Local...</code> (or <code>Archive...</code>, for an unpacked zip.)
 
To import such a folder, use <code>Help > Software Updates... > Available Features > Manage sites... > Add... > Local...</code> (or <code>Archive...</code>, for an unpacked zip.)
 +
 +
''This doesn't feel exactly the same as old "Extension Location". After adding local feature you still have to manually select available features and explicitly install them, while with old update manager, linked "Extension Locations" were installed automatically.''
 
</td>
 
</td>
 
</tr>
 
</tr>

Revision as of 09:59, 19 May 2008

This is a work in progress, and subject to change.

Before & After

Below is a comparison chart showing how to organize your extensions, plugins & features, using a p2-free Eclipse and a p2-enabled Eclipse (3.4M6+).

Eclipse 3.2 through Eclipse 3.4M5 Eclipse 3.4M6+
 
Eclipse
folder
eclipse/
  plugins/  (plugin folders & jars)
  features/ (feature folders)
eclipse/dropins/somefolder/eclipse/
  plugins/  (plugin folders & jars)
  features/ (feature folders)

- or, simpler -

eclipse/dropins/eclipse/
  plugins/  (plugin folders & jars)
  features/ (feature folders)

Note that the old layout is also still supported, but with the new dropins folder, you have more control and it's easier to clean up unwanted extensions (eg., by deleting the whole somefolder folder).

 
.link
files
eclipse/links/ (*.link files)
eclipse/dropins/ (*.link files)

As before, each .link file contains a path to a folder in which eclipse/features/ and eclipse/plugins/ can be found. For example:

path=/home/nickb/eclipse/phpeclipse

- or -

path=X:/home/nickb/eclipse/ecf

Note that the old layout is also still supported.

 
Extension
folders
.../somefolder/eclipse/
  plugins/  (plugin folders & jars)
  features/ (feature folders)
  .eclipseextension

These folders, including the .eclipseextension file, are created when doing an Update Manager install to a folder other than the base eclipse/ directory.

If you want to create the .eclipseextension file by hand, here's how. You can also just open the .eclipseproduct file from the root of your Eclipse install with Eclipse's File > Open File... then do a File > Save As... to rename it.

To import a pre-existing folder, use Help > Software Updates > Manage Configuration > Add an Extension Location.

.../somefolder/eclipse/
  plugins/  (plugin folders & jars)
  features/ (feature folders)

The old format is still supported, though the .eclipseextension file is no longer required.

As such, you can now just unpack a zip and point Eclipse at it. Or, even easier, point Eclipse at the zip and it'll handle the unzip for you.

To import such a folder, use Help > Software Updates... > Available Features > Manage sites... > Add... > Local... (or Archive..., for an unpacked zip.)

This doesn't feel exactly the same as old "Extension Location". After adding local feature you still have to manually select available features and explicitly install them, while with old update manager, linked "Extension Locations" were installed automatically.

See Also