Community
Participate
Working Groups
I20070418-1012 I have noticed that when I change my target environment the plug-in dependencies do not get updated which can cause problems. Here are steps to reproduce: - start eclipse - create a plug-in with some UI dependencies - expand the plug-in dependencies and notice that the swt fragment for your platform is present. good. - change the target platform to point at an RCP based target containing the delta pack. reload. apply. the plug-in dependencies are left unchanged. good. - now modify the environment variables in the target platform to something else, notice that the reference to the swt fragment is not modified properly.
CC'ing Wassim so he can review patch when it is ready.
Created attachment 66943 [details] patch The patch contains code that was refactored out of MinimalState into TargetPlatformHelper, so that we calculate the platform properties using the same method no matter where we are. When the user selects OK on the TargetEnvironmentTab, we check to see if any of the values have changed. If they have, we get the "current state" (either the ModelManger's state or a new PDEState if the user choose a new target), and reset the platform properties. If the current state == the ModelManager's state (meaning the user did not load a new target), we send an event to the ModelManager to reresolve the state since the platform properties have changed. If the current state != the ModelManager's state, there is no reason to send the event since all the Workspace projects will get refreshed when the state gets reset.
Released patch. Brian is awesome.
