Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 359436

Summary: Investigate defining browsers / runtimes to use for debugging
Product: [WebTools] JSDT Reporter: Michael Rennie <Michael_Rennie>
Component: DebugAssignee: Orlando Rincon <orlandor>
Status: RESOLVED FIXED QA Contact: Michael Rennie <Michael_Rennie>
Severity: enhancement    
Priority: P3 CC: cbridgha, curtis.windatt.public, gorkem.ercan, psuzzi, thatnitind, vrubezhny
Version: 3.4   
Target Milestone: 3.8 M6   
Hardware: All   
OS: All   
See Also: https://git.eclipse.org/r/67764
https://git.eclipse.org/r/68460
https://git.eclipse.org/c/jsdt/webtools.jsdt.git/commit/?id=629f22fade95afab67024c3e66afef0b22329795
https://git.eclipse.org/c/jsdt/webtools.jsdt.git/commit/?id=eba46d224ad6591a42dabf5a495833783a62e8fc
Whiteboard: RHT
Bug Depends on:    
Bug Blocks: 488975    

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