Bugzilla – Full Text Bug Listing
| Summary: | Rhino Debug Launcher has the same CWD as Eclipse | ||
|---|---|---|---|
| Product: | [WebTools] JSDT | Reporter: | Jonas Lund <whizzter> |
| Component: | Debug | Assignee: | Project Inbox <jsdt.debug-inbox> |
| Status: | NEW --- | QA Contact: | Michael Rennie <Michael_Rennie> |
| Severity: | major | ||
| Priority: | P3 | CC: | thatnitind |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
(In reply to comment #0) > Suggested solution: The Java launcher has an option in the arguments tab where > one can select the default working directory ${workspace_loc:PROJECTNAME} or > specify a custom working directory. Mimicing this behaviour of the Java > Launcher would be highly recommended since it works very well. I agree it would be helpful to be able to specify the working directory. In the meantime if you are using the 'Rhino JavaScript' launcher you can always specify the scripts / folder on the 'Include' tab |
When the Rhino Debug Launcher invokes a script the current working directory is the working directory of Eclipse, so invoking f.ex. load("scriptname.js") will fail to load another script in the same directory as the originating script, also loading other resources will fail (same again.. the current working directory is eclipse's and not the invoking script or project). Suggested solution: The Java launcher has an option in the arguments tab where one can select the default working directory ${workspace_loc:PROJECTNAME} or specify a custom working directory. Mimicing this behaviour of the Java Launcher would be highly recommended since it works very well.