Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 359436 - Investigate defining browsers / runtimes to use for debugging
Summary: Investigate defining browsers / runtimes to use for debugging
Status: RESOLVED FIXED
Alias: None
Product: JSDT
Classification: WebTools
Component: Debug (show other bugs)
Version: 3.4   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 3.8 M6   Edit
Assignee: Orlando Rincon CLA
QA Contact: Michael Rennie CLA
URL:
Whiteboard: RHT
Keywords:
Depends on:
Blocks: 488975
  Show dependency tree
 
Reported: 2011-09-29 11:07 EDT by Michael Rennie CLA
Modified: 2016-04-08 18:10 EDT (History)
6 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Rennie CLA 2011-09-29 11:07:08 EDT 
Akin to JDT's notion of an installed JRE (EE), we should investigate being able to define browsers (Firefox et. al.) and runtimes (node.js, Rhino, etc) that can be used to run / debug with.
Comment 1 Chuck Bridgham CLA 2016-01-26 10:47:43 EST 
Started to look at this...

Currently the org.eclipse.wst.jsdt.launching package holds the classes that were "borrowed" from JDT to represent the JS environment.  

Currently the org.eclipse.wst.jsdt.launching.IVMRunner class is used to launch js applications.  

We need proper interfaces for 
JSEngine(Rhino, V8, Nashorn etc..)
JSRuntimeEnvronment(Node.js, Firefox, Chrome etc..)
Comment 2 Eclipse Genie CLA 2016-03-03 13:24:32 EST 
New Gerrit change created: https://git.eclipse.org/r/67764
Comment 3 Eclipse Genie CLA 2016-03-15 13:38:58 EDT 
New Gerrit change created: https://git.eclipse.org/r/68460