Tips to Updating and Upgrading with Eclipse, Page 4
Eclipse allows the use of multiple versions on the same machine, so you will want to decide if is preferable for you to create new workspaces so that you can continue to use your older version, or simply point to the existing workspaces. Both approaches are accomplished through the Import menu; the difference is whether you select the Copy to New Workspace option.
Figure 11: Importing Projects
Next, check your plug-ins. In some cases, your preferences will have been imported from your .epf file. In other cases, the preferences were stored on a workspace level. If they were stored there and are not available after importing your projects, go to the.metadata\.plugins path in your backup and you will find the setting stored under the individual plug-in. In some cases, you will simply need to re-configure the plug-in manually, either because the plug-in stored the information in an OS-based path or because the configuration syntax changed between versions.
The Eclipse builds are one of the most stable Open Source projects around. Updates are rarely necessary anymore unless required by a plug-in, and when they are necessary they are simple and painless to run. How easy or difficult a full upgrade will be depends on the plug-ins you use. Hopefully, the steps covered in this article will minimize or even eliminate any difficulties when a full upgrade makes sense for your development needs.
About the Author
Scott Nelson provides optimization services designing, developing, and maintaining web-based applications for manufacturing, pharmaceutical, financial services, non-profits, and real estate agencies for use by employees, customers, vendors, franchisees, executive management, and others who use a browser. For information on how he can help with your web applications, please visit http://www.fywservices.com/. He also blogs all of the humorous emails forwarded to him at Frequently Unasked Questions.
Page 4 of 4