Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 365996

Summary: SourceLocatorId ans SourcePathComputerId defined in the preferred launch delegate should be preferred over the default one specified in launch configuration type.
Product: [Eclipse Project] Platform Reporter: Thirumala Reddy Mutchukota <thirumala>
Component: DebugAssignee: Platform-Debug-Inbox <platform-debug-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: tparker
Version: 3.7   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard: stalebug

Description Thirumala Reddy Mutchukota CLA 2011-12-08 04:45:10 EST
Build Identifier: I20110613-1736

Existing behavior:
The sourceLocatorID or sourcePathComputerID of a launch configurations are found in the following way ...
(1) If they are defined in launch configuration itself use them.
(2) If not found in (1), look for them in launchConfigurationType extension point and use them if they are found there.
(3) If not found in (2), look for them in launchDelegate extension point of preferred launch delegates of this launch configuration and use the first one found.

Problems with this behavior:
(1) When the default sourceLocatorId and sourcePathComputerId are defined in the launch configuration type extension, it's not feasible to use different sourceLocaIds for different preferred delegates of that launch configuration, as the default one always takes higher precedence over the one defined in the preferred launch delegates.
(2) When the default sourceLocatorId and sourcePathComputerId are defined in the launch configuration type extension, the only way to use a different sourceLocatorId or sourcePathComputerId as saving them into the every launch configuration even though the same are added to the preferred launch delegate.

To solve these problem the better way of handling them is:
(1) If they are defined in launch configuration itself use them.
(2) If not found in (1), look for them in launchDelegate extension point of preferred launch delegate and use them if they are found there.
(3) If not found in (2), look for them in launchConfigurationType extension point and use them if they are found there.

Reproducible: Always
Comment 1 Eclipse Genie CLA 2019-10-12 03:38:14 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.