Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Equinox p2 Migration Guide"

(migration guide for old eclipse plugins/features moving to p2-enabled eclipse)
 
m
 
(5 intermediate revisions by 3 users not shown)
Line 5: Line 5:
 
==Before & After==
 
==Before & After==
  
Below is a comparison chart showing how to organize your extensions, plugins & features, using a pre-p2 Eclipse and a post-p2 Eclipse (3.4M6+).  
+
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+).  
  
 
<table>
 
<table>
Line 66: Line 66:
 
   features/ (feature folders)
 
   features/ (feature folders)
 
   
 
   
The old format is still supported, though the .eclipseextension file is no longer required.  
+
External Extension Locations aren't supported anymore. You can only import the old extension directories content into the Eclipse plugins and features directories. All files from that external Extension Locations will then be copied into the folders under the Eclipse root folder.
 +
For the import 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.  
+
You can 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 <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 the same as old "Extension Location". After adding a 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. Furthermore there is no more UI support to install plugins into Extension Locations, all plugins go directly under the Eclipse root directory.''
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 79: Line 82:
 
* [[Equinox_p2_Getting_Started|Equinox p2 - Getting Started]]
 
* [[Equinox_p2_Getting_Started|Equinox p2 - Getting Started]]
 
* [[Equinox_p2_Getting_Started#Dropins|Equinox p2 - Getting Started with Dropins]]
 
* [[Equinox_p2_Getting_Started#Dropins|Equinox p2 - Getting Started with Dropins]]
 +
* [[Equinox_p2_tests|Equinox p2 Testcases]]
  
 
+
[[Category:Equinox_p2|Migration]]
[[Category:Equinox_p2]]
+

Latest revision as of 15:07, 21 June 2010

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)

External Extension Locations aren't supported anymore. You can only import the old extension directories content into the Eclipse plugins and features directories. All files from that external Extension Locations will then be copied into the folders under the Eclipse root folder. For the import the .eclipseextension file is no longer required.

You can 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 the same as old "Extension Location". After adding a 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. Furthermore there is no more UI support to install plugins into Extension Locations, all plugins go directly under the Eclipse root directory.

See Also

Back to the top