Community
Participate
Working Groups
Build Identifier: I20090611-1540 Here's an example of such a problem: Consider the ${project_loc} variable, which optionally takes a variable. If the variable is missing, then it looks for a selection from either the selection service or the editors. But let's talk about varaible resolution on the part of the launching framework. So, there you have a launch configuration that's typically associated with a project.*1 Suddenly ${project_loc} takes on a new meaning. So let's say I have two projects, named Foo and Bar, and their locations are /path/foo and /path/bar. So if I create a launch configuration (Heck, let's say a Java Application) and set the project to "Foo". Then we set the working directory to ${project_loc}. Save it. Don't launch it yet. Now make sure no files are open in the editor. Then in the Project Explorer select '/Bar'. Now launch the new launch configuration. The working directory is /path/bar. What?? The launch configuration's project is Foo? Why shouldn't the working directory be /path/foo? More to the point, what if I have started Eclipse, not selected anything, and tried launching that configuration? It won't be able to resolve ${project_loc} even though the launch configuration has a project. Now, this very _specific_ example is not my genuine issue, because my specific issue is that I'm creating variable resolvers that are meant to provide project-specific metadata (I have a custom nature.) This same issue comes up. *1 Granted, each launch configuration type can specify a project, so strictly speaking this isn't necessary. Reproducible: Always
This is a known issue, and other similar bugs have been reported in the past (for example, bug 170789). The existing variable resolution API does not support a "context" for resolution. The String variable substitution API would need to be enhanced to accept some sort of context when resoling variables in order to achieve this. I believe this should be marked as an enhancement request to support contexts for variable resolution.
Darin, thanks for the reply. Yeah I assumed it was a known issue, but it was hard for me to find an existing bug! So the reference to 170789 is helpful, thanks. I'm going to probably work around this for now by doing some slightly ugly things (as opposed to moderately ugly things.) Since this is the debug component, I'll ask: can multiple launch configurations be launched in parallel? Or is there some sort of infrastructure lock or guarantee that only one ILaunchConfiguration.launch method is called at a time?
(In reply to comment #2) > Since this is the debug > component, I'll ask: can multiple launch configurations be launched in > parallel? Or is there some sort of infrastructure lock or guarantee that only > one ILaunchConfiguration.launch method is called at a time? There is nothing in the platform preventing this. It should be possible. (Of course, I'm not sure anyone has tried it...)
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.
If someone wants to work on this we can look into it.
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. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. 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.
