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.
Difference between revisions of "FAQ How do I install new plug-ins?"
m (formatting) |
|||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
Your best approach is to use the Eclipse Update Manager. | Your best approach is to use the Eclipse Update Manager. | ||
| − | + | More experienced plug-in developers — and sometimes lazy plug-in | |
| − | + | publishers — have learned to find the <tt>eclipse/plugins</tt> directory and | |
| − | More experienced plug-in developers | + | |
| − | publishers | + | |
install their plug-ins there manually. This obviously is | install their plug-ins there manually. This obviously is | ||
a more dangerous approach, as no certification takes | a more dangerous approach, as no certification takes | ||
place about the suitability of the plug-in; it may rely | place about the suitability of the plug-in; it may rely | ||
on other plug-ins not available in your installation. | on other plug-ins not available in your installation. | ||
| − | In the case of compatibility conflicts, you won | + | In the case of compatibility conflicts, you won't find out |
until you use the plug-in that it might break. | until you use the plug-in that it might break. | ||
| − | |||
| − | |||
You may compare installing plug-ins to installing applications | You may compare installing plug-ins to installing applications | ||
| Line 24: | Line 20: | ||
as the Eclipse equivalent of InstallShield and the Windows | as the Eclipse equivalent of InstallShield and the Windows | ||
Registry combined. | Registry combined. | ||
| − | |||
| − | |||
For day-to-day development and prototyping of small plug-ins, | For day-to-day development and prototyping of small plug-ins, | ||
| Line 35: | Line 29: | ||
ready from the start will make it much easier to boast of your Eclipse | ready from the start will make it much easier to boast of your Eclipse | ||
knowledge to your friends and colleagues. | knowledge to your friends and colleagues. | ||
| − | |||
| − | |||
| − | |||
| − | |||
== See Also: == | == See Also: == | ||
| − | |||
[[FAQ_How_do_I_create_a_plug-in%3F]] | [[FAQ_How_do_I_create_a_plug-in%3F]] | ||
| − | |||
[[FAQ_How_do_I_create_a_feature%3F]] | [[FAQ_How_do_I_create_a_feature%3F]] | ||
| − | |||
[[FAQ_What_is_the_Update_Manager%3F]] | [[FAQ_What_is_the_Update_Manager%3F]] | ||
| + | [[FAQ_What_is_the_purpose_of_activities%3F]] | ||
| − | [ | + | <hr><font size=-2>This FAQ was originally published in [http://www.eclipsefaq.org Official Eclipse 3.0 FAQs]. Copyright 2004, Pearson Education, Inc. All rights reserved. This text is made available here under the terms of the [http://www.eclipse.org/legal/epl-v10.html Eclipse Public License v1.0].</font> |
Latest revision as of 11:39, 10 February 2016
Your best approach is to use the Eclipse Update Manager.
More experienced plug-in developers — and sometimes lazy plug-in publishers — have learned to find the eclipse/plugins directory and install their plug-ins there manually. This obviously is a more dangerous approach, as no certification takes place about the suitability of the plug-in; it may rely on other plug-ins not available in your installation. In the case of compatibility conflicts, you won't find out until you use the plug-in that it might break.
You may compare installing plug-ins to installing applications on Windows. You can, of course, install your dynamic link libraries (DLLs) in the System32 directory or play with the PATH environment variable. But, how are you going to remove the application later when you no longer need it? On Windows, specialized installation programs have been devised, and uninstallation is easy through the Start menu. The Eclipse Update Manager can be seen as the Eclipse equivalent of InstallShield and the Windows Registry combined.
For day-to-day development and prototyping of small plug-ins, you might still be tempted to use the manual installation process. You could, but we strongly advise against it. Creating a feature and a corresponding update site is child’s play using the PDE wizards and will greatly improve the quality of your work. Eventually, you will want to share your fruits with others, and having an update site ready from the start will make it much easier to boast of your Eclipse knowledge to your friends and colleagues.
See Also:
FAQ_How_do_I_create_a_plug-in?
FAQ_How_do_I_create_a_feature?
FAQ_What_is_the_Update_Manager?
FAQ_What_is_the_purpose_of_activities?
This FAQ was originally published in Official Eclipse 3.0 FAQs. Copyright 2004, Pearson Education, Inc. All rights reserved. This text is made available here under the terms of the Eclipse Public License v1.0.