Thanks firstHave anybody updated Eclipse through correct procedure by Updater?
What is the Right Way to Update?2.1 M4 build was my first Eclipse update from build 2.1 M3. First I have tried to use Update Manager but without much success, it probably was designed to handle major releases and not builds. My first impulse was to reinstall everything from the scratch. Then what to do with my preferences, projects and plugins? The easiest way was to create a new directory and install a new build of eclipse into it, then copy workspace directory from the previous build. That will take care of preferences and projects. And if builds are backward compatible you are fine, and if smth. is wrong you have the previous build intact. That is the main reason why I prefer installation into a new directory. For a build, even a stable one, it is safer to install into a new directory. Then you need to deal with the plugins that did not come with Eclipse but were installed separately. I found that it is usually a good idea to install the plugins into external directory. That will make the extra installed plugins nicely separated from the ones that came with Eclipse. And you can share the external plugin directory between different Eclipse installations and even between developers. It is also easier to experiment with new plugins. You will have two different installations, one for Eclipse and one for the external plugins. Next you need to establish relationship between the external plugin directory and Eclipse. But it turned out to be not as simple as having external folders for Eclipse projects. You need to create the external plugin directory as a Product Extension, you do this by creating directory structure as described in Eclipse docs with .eclipseextension er file. The external plugin directory should have an eclipse subdirectory with eclipse\features and eclipse\plugins subdirectories, see Directory Structure chapter. Then in the Eclipse installation you need to create link directory with a link file. The link file is a java.io.Properties format file, which defines the path to the external plugins directory. In docs there are rules for the link file names and if I understood them correctly you might need different link files for different plugins but I followed swiki recommendation to use name .link and it looks sufficient as one link file for all plugins. Maybe different link files are needed when you have more than one external plugins directory, but I never had more than one. You can also link your external plugin directory manually using Update Manager. Open Update Manager and in the "Feature Updates" view navigate to the external plugins directory, and if a er file is present you will see an extension icon, right-click on it, on pop-up menu click Link Product Extension, you might need to restart Eclipse. If you prefer to link manually then you probably don't need link directory. If you have a link directory it looks that you can get away without a er file but docs says that you need both. This script creates an external plugins directory as a product extension with a er file and creates a link directory too. When updating to a new build you will also need to update the er file in the external plugins directory. That is what this script does and it also creates eclipse.bat file for windows users to start eclipse with your favorite jvm. What drives me crazy is to remember all these small bookkeeping details and this script will do it for you. Even if you want to update Eclipse manually this script will serve you as an update manual.Unfortunately plugin writers are not consistent in directory structure. Not all plugins have plugins directory, no pun intended. If a plugin has features directory then it has plugins directory as well. If a plugin doesn't have features directory it is still a good idea to have plugins directory in .zip file, even if it is obvious that installation should go into plugins directory. Because of this install-plugins target became rather complicated. It is probably a good idea to execute backup-workspace target before experimenting with a new plugin. uninstall-eclipse target will always backup the workspace. If you are installing Eclipse over an existing installation then install-eclipse target will backup external workspace, internal workspace will be copied from the previous installation.http://home.nyc.rr.com/olegs/eclipse/antscript/readme.htm#the%20Right%20Way%20to%20Update你看一下是否解决问题
解决方案 »
免费领取超大流量手机卡，每月29元包185G流量+100分钟通话, 中国电信官方发货