Community
Participate
Working Groups
Build Identifier: I20101028-1441 Opening a run configuration (that has been stored as a "shared file") in the run configuration dialog is enough to make Eclipse rewrite the corresponding .launch file. This is especially annoying when keeping such a file under version control as the list of "selected_target_plugins" is reshuffled randomly... I'd expect the the file to remain untouched unless I make a change and hit "Apply" (or otherwise confirm that I want the change to be saved). Reproducible: Always
Needs investigation. Most of these kinds of issues should have been fixed in 3.6.
Did you change the contents of your target platform? The selected target plug-ins will be updated if the target plug-ins change. We do this silently otherwise your launch configuration would quickly become stale if you updated your target platform. I tried some other use cases and had no issues. Opening the configuration doesn't change the list. Opening the config and unchecking/checking a target plug-in does not change the list (we fixed this in 3.6).
Perhaps there is something about my target platform definition that is confusing Eclipse? <location path="${project_loc}" type="Directory"/> <location includeAllPlatforms="false" includeMode="planner" type="InstallableUnit"> <unit id="org.eclipse.sdk.ide" version="3.6.1.M20100909-0800"/> <repository location="http://download.eclipse.org/eclipse/updates/3.6"/> </location>
(In reply to comment #3) > Perhaps there is something about my target platform definition that is > confusing Eclipse? > > <location path="${project_loc}" type="Directory"/> > <location includeAllPlatforms="false" includeMode="planner" > type="InstallableUnit"> > <unit id="org.eclipse.sdk.ide" version="3.6.1.M20100909-0800"/> > <repository location="http://download.eclipse.org/eclipse/updates/3.6"/> > </location> If you use the project_loc variable without a resource specified it resolves based on the selection. Perhaps your target is resolving to different things at different time causing the contents of the launch to change.
Closing as WORKSFORME. We are not able to reproduce, and the target definition provided is using a variable which may change its contents.
Just tested again with 3.6.2. Looks like .launch files are not rewritten each time I open them, but only after I open the target platform definition and do "Set as Target Platform" (after making some meaningless changes). When I then open a launch configuration, the .launch file is rewritten (i.e. the list of plugins is rearranged randomly). Note that if the list of plugins were kept in alphabetical (rather than random order) this wouldn't be an issue.
This is related to some of the behaviour that is going on in bug 309701. I've been looking at that defect and have added some notes. Certainly the following steps will produce a spurious save that ends up in different versions of the launch file. I have NOT seen the plugin re-ordering but have seen the config location change and the run levels and autostart values of plugins change. I see this behaviour on both 3.6.2 M20110210-1200 and head of 3.7. I have a potential fix for the configLocation problem and a good problem description of the run level changes. Steps to reproduce: 1) Create a new launch config 2) Change the launch config name 3) Press Deselect All on the Bundles tab 4) Select a couple of Bundles 5) Press the Add Required Bundels button 6) Open the Common tab, Select Shared file and select project in your workspace 7) Apply and Close the dialog 8) Copy the created .launch file 9) Reoopen the launch confg 10) Close the launch config 11) Compare the new launch config and the copy you made in step 8 You will see that the 1st launch config has an incorrect configLocation and incorrect run and autostart values on some bundles, the 2nd launch config has this corrected configLocation and run levels. The problem that I am seeing, in both cases, is that the config models are saved before they are updated appropriately. After the save, the dialog input is set to the correct working model. Code paths run that correctly set the run levels and configLocation, this dirties the editor causing the save.
*** Bug 327722 has been marked as a duplicate of this bug. ***
This bug is a duplicate of Bug 329308. I lack sufficient privileges to set it as a duplicate, could somebody please make the change. I will be attaching a patch to Bug 329308 that should solve the ordering problem when changing targets as well as some other problems noted in Bug 329308 that also cause changes to show up.
*** This bug has been marked as a duplicate of bug 309701 ***
