Community
Participate
Working Groups
When using a launch file it is necessary to set a working directory. There are lots of interesting variables but none is relative to the launch file. If a launch file is copied to another project or another directory, the reference to the old position remains in the launch file. Relative path names are quite crucial to ease migration and reuse. Eclipse supports this with variables, so the ommission of the launch file relative variable was surprising.
This feature request has the same difficulty as bug 117748. That is, we have no way of resolving the location of a file without passing in a context (i.e. path to the file). The current variables that resolve to files require workspace relative paths. Of course, if you move/rename the referenced file, the variable argument becomes stale. The existing string substitution support does not allow for arbitrary contexts to be used when resolving variables - it relies only on the expression being resolved such that any client can resolve any string containing variables.
Not planned for 3.2
As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you.
