Bugzilla – Full Text Bug Listing
| Summary: | The Launcher should support variables | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Markus Kohler <kohler> |
| Component: | Debug | Assignee: | Darin Wright <darin.eclipse> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | colinml1, eclipse, eric.estievenart, jan, jean-michel_lemieux, jgossage, kari.ikonen, max, nikolaymetchev, olsok, paduffy, skeet |
| Version: | 2.0 | ||
| Target Milestone: | 3.0 | ||
| Hardware: | PC | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Markus Kohler
Our current story is that a launch config can either be sharable or local. Launch configs that depend on local file system paths should not be defined as sharable. Variables would increase the reusability shared launch configs. To do so the current Classpath variables support could be generalized to workspace variables. This is not the first request for this. We should get more feedback on this once more people are starting to use launch configs. Moving to Debug. You can now specify a working directory relative to the workspace or a project. See the new changes in the "Arguments Tab" for "Local Java Applications". *** This bug has been marked as a duplicate of 14977 *** How to I specify a working directory relative to the project dir ? I store my build results above the project dir. If the project is for example stored at D:\projects\MyProject then the build results might go to D:\_build\MyProject. One way to solve the problem could be to create a new project within the workspace just for the build results and then reference the working directory using this project. Is this the recommend way to do it ? To specify a project relative working directory, you must specify a project name (i.e. workspace relative). As suggested, you could create a project for this purpose. We do not intend to add support for variable working directories in 2.0. Marking as "Later" for future consideration. *** Bug 31893 has been marked as a duplicate of this bug. *** *** Bug 33663 has been marked as a duplicate of this bug. *** Re-opening for 3.0 *** Bug 37638 has been marked as a duplicate of this bug. *** *** Bug 28340 has been marked as a duplicate of this bug. *** Support for context-specific variables has been moved from the UI External Tools plugin to the Debug UI plugin (Bug 36930). Once support for "core variables" has been added to Debug Core (Bug 37241), I'll add support for variables to launch config types defined in Debug and JDT Debug. *** Bug 29971 has been marked as a duplicate of this bug. *** *** Bug 37891 has been marked as a duplicate of this bug. *** Further suggestions, things we MUST to be able to do within VM args (in psuedo
Win2K speak).
-DXXX=${project_loc}/a/b/c
-DYYY=%XXX%;/c/d/e
-DPATH=${project_loc}/x/y/x;%PATH%
*** Bug 40311 has been marked as a duplicate of this bug. *** *** Bug 41855 has been marked as a duplicate of this bug. *** Suggest to add support for variables in * program args * vm args * working directory Added support as specified. Also, filed but 45691 to address UI enhancements to make entering variables easier and the feature more apparent. Please verify the core support for variables in Java configs, DarinW. Changes to AbstractJavaLaunchConfigurationDelegate. NOTE: Please file any requests for variable support in other specific locations as separate bugs. Verified (I will file a new bug for a problem I found with the working directory). |