Eclipse Plugin Installation Summary

Eclipse plug-in installation summary through the personal learning experience, the current Eclipse plug-in installation of three ways, summarized as follows:

The first approach is simple, with a plugins directory and features directory under ECLIPSE's home directory (%eclipse_home%). After the plug-in decompression, in the extracted folder can generally see the plugins folder, and some plug-in decompression can also see a features folder. In general, the contents of the plugins folder are copied directly to the%eclipse_home%/plugins directory, if there is a features folder under the extracted plug-in directory, the contents of the folder will also be copied to the%eclipse_home%/ Under the features. After you restart Eclipse, you can use the plug-in you just installed. If the plug-in is not available, it may be because the plugin is not enabled. can go to help/software updates/manage configuration under the "Disable" plug-in "Enable" can. This plug-in installation method is simple, fast, but defective, if too many plug-ins, will make the content very confusing, and can not tell which is the system comes with, which is installed later. When many plugins are installed, Eclipse becomes large, making it easier to update and manage many plugins. Each time you reinstall Eclipse, you'll take the time to install the few common plugins.

The second approach is also simple, with the help of the Eclipse Wizard to install the plugin. With Help/software Updates/find and Install, select "Search for new features to Install" in the pop-up menu, click "Next" and select "New Local Site" in the next menu or "New archived Site", locate the directory where you downloaded the plugin, select Install. This method installs the plug-in is relatively safe, is not easy to mistake, the disadvantage is for the plug-in request is also more fastidious, therefore can support this way installs the plug-in also relatively few. General requirements in the plug-in directory not only the plugins and features folders, but also the Site.xml file (Site.xml is the configuration file for automatic installation, eclipse will automatically install the plugin based on the information of the file). The Eclipseme plugin that supports J2ME development is installed in this way.

The third way is to create a links directory under the ECLIPSE home directory, and then place your own plugin anywhere you want, this time you put the plugin directory is the plugin directory (%plugin_home%), and then in your%eclipse_home%/links/ Directory to create a link file, such as to install a VSS plug-in, you can create a Vss.eclipse.link file in the links directory, the name of the link file to pick. This vss.eclipse.link file points to the directory that holds the VSS plugin (%plugin_home%). If your VSS plugin's Zip/rar file is decompressed and placed under C:/eclipse_plugins/vss.eclipse (if the plug-in is a jar file, you can not unzip it), the contents of the Vss.eclipse.link file should be: path= C://eclipse_plugins//vss.eclipse. Note: The file path referred to by path must be separated by adding a "/" escape character. In this way to install plug-ins to have a certain attention. That is, you must have the Eclipse directory under the plugin directory, and then build features and plugins separately under the Eclipse directory. For example, if Vss.eclipse.zip is decompressed into a vss.eclipse directory, this directory contains a plugins subdirectory. Create a new subdirectory in the Vss.eclipse directory eclipse, and then move the plugins directory to the newly created Eclipse directory, and then create a features directory under the Eclipse directory that you just created. That is, the directory structure if this: C:/eclipse_plugins/vss.eclipse/eclipse/plugins,
C:/eclipse_plugins/vss.eclipse/eclipse/features. The Eclipse directory structure does not need to be established if the other compressed files are already included in the Eclipse/plugins, Eclipse/features directory. After you start eclipse, Eclipse goes to the directory specified in the link file to find the Eclipse/features directory and the Eclipse/plugins directory to see if there are legitimate features and plugins. In other words, the destination directory must contain a/eclipse directory. If found, additional features and plugins are available at run time, and if the linked files are added after the workspace is created, the additional features and plugins are processed as new configuration changes. For a description of the third way:
1. Plug-ins can be installed in a number of custom directories, respectively;
2. A custom directory can install multiple plugins;
3. link file filename and extension can take any name, such as Ddd.txt,myplugin can;
4. The path path of the Path= plugin directory in the link file is separated by "//" or "/";
5. You can also have multiple link files in the links directory, and the path parameter in each link file will take effect;
6. The plugin directory can use relative paths;
7. You can set up a subdirectory in the links directory, such as disable, to transfer temporarily unused plugins to this subdirectory, to speed up eclipse startup;
8. about installing the Lomboz plugin with links, you may have problems editing the EJB. The benefits of this approach can be categorized into the management of plugins. If a plug-in is already installed and you want to reinstall it, simply replace the file or modify the link file's path. When you reload eclipse, simply copy the original Eclipse links directory directly to the new eclipse, and then copy the plugin directory to the new eclipse appropriate directory. And then it's all packed up in-clean mode. The Common Java EE development tool--myeclipse is to organize plugins in this way. Together for Eclipse is also a typical installation using the links method. In general, after installing the plugin in the above three ways, the plugin will not take effect until the eclipse is restarted. If not, you can follow these steps to check:
1. First take a look at the plugin loading list in the about, and if not, confirm that the dependency plug-in for the installed plug-in is already installed. Eclipse plug-ins are dependent, in each plug-in plugin.xml in the <requires> tag, the inside of each <import> tag represents the dependent plug-in, Eclipse will load the plug-in according to the dependency of the plug-in at startup, if the plug-in cannot be found, the installed plug-in may not run properly;
2. If the loaded plugin list already has, it may be not open this plugin view or need to configure something in the preference to be effective, This is the best look at the installed plug-in Plugin.xml, see it has expanded the extension points, the menu is nothing more than actionsets this extension point, the interface is the views of this extension point, can be set in Show view, there are some other extension points, can be specific problems specific analysis ；
3. The most effective way: look at log. In the Eclipse installation directory Workspace/.metadata subdirectory (if the default workspace is not used, the directory structure may be different) there is a. log file from which you can generally find the cause of the failure;
4. If the plug-in is still not installed, remove the Org.eclipse.update directory under the Eclipse installation directory configuration subdirectory and restart.   A third way of personal recommendation