Community
Participate
Working Groups
To support the cancelation of the creation/editing/deletion of multiple launch configurations from a property page, using existing launch configuration editing infrastructure (i.e. opening the launch dialog from the property page), we require nested working copies. Nested working copies allows a working copy B to be created from a launch configuration A. It then allows a nested working C to be created from B. When C is saved, its changes are written to its parent working copy B. When B is saved, its changes are persisted back to its original launch configuration A. (In the past all when a working copy was saved it was always written back to the original configuration A). This support has been released in support of but 74480.
The methods ILaunchConfigurationWorkingCopy.getParent() has been added, and the doSave() methods has been updated to save changes to parent or original based on the nested level of a configuration.
Marking verified. Philippe, I added this bug to track the API change for nested working copies.