Community
Participate
Working Groups
Detailed Problem description: ========================== Each workspace in Eclipse has it's set of environment or workspace variables which seems wrong. There are variables which the user cannot change via the gui as they are set at install time eg JRE_LIB. However, during the process of uninstalling one build and replacing with another I changed my installation path. This meant that all my workspaces were pointing to incorrect path locations. To fix this I had to edit a file :- E:\WebSphere Studio Workspaces\wsad\ma\.metadata\.plugins\org.eclipse.jdt.core\pref_store.ini for each workspace. These values should surely be part of the core product and as such would be refreshed automatically. Although a normal user would not be moving from build to build they might have a need to copy a workspace from one installation of WSAD v5 to another. If the two installations are in different directories this will become and issue - and one which could surely be avoided. In addition when starting the help for the first time the help system is indexed. But it is indexed again for each new workspace. Couldn't there just be one index for the base installed used by all workspaces - or even better just tag the indexing onto the back of the install process so that the help is available for use immediately? The user probably wouldn't notice another 30secs to a minute on the install but does notice it when they need to use the help for the first time.
The issue of sharing various settings across multiple workspaces is captured in the following plan item bug report: https://bugs.eclipse.org/bugs/show_bug.cgi?id=36965 JRE_LIB is not hard-coded, as it can be changed in the UI from Preferences > Java >Installed JREs. However, I have added a reference to your problem case in the plan item bug report. I'm going to close this as a duplicate. Please open a separate bug report for the Help indexing issue (Product=Platform, Component=Help). It is difficult for us to track bug reports that raise issues across several components. *** This bug has been marked as a duplicate of 36965 ***