[
https://issues.jboss.org/browse/ERT-47?page=com.atlassian.jira.plugin.sys...
]
Ilya Buziuk commented on ERT-47:
--------------------------------
[~dgolovin], After investigating both JSDT & Chromium breakpoint model
!breakpoints.png|thumbnail! I have figured out that using correct annotation id is not
the only thing that should be changed to make it work. The main action happens in
*BreakpointSynchronizer* which use *ChromiumBreakpointAdapter* -
https://github.com/ChromeDevTools/cdt-java/blob/master/plugins/org.chromi...
for breakpoint sync
So, if the JSDT breakpoint would be created with the correct Marker attributes mapping
will not work - in order to make it work adapter should recognize and process JSDT
breakpoint correctly. The main problem is that many things are coupled to
ChromiumLineBreakpoint class directly, so it seems that the architecture should be changed
to make those two work / sync correctly.
Translate breakpoints from .js files to Chromium/Node V8 JavaScript
Engine [EBZ#486061]
---------------------------------------------------------------------------------------
Key: ERT-47
URL:
https://issues.jboss.org/browse/ERT-47
Project: Eclipse Release Train
Issue Type: Task
Components: JSDT
Reporter: Max Rydahl Andersen
Assignee: Ilya Buziuk
Labels: Debug, bzira
Attachments: breakpoints.png
Current implementation in ChromeDevTools can map breakpoints from files in workspace to
running VM. Problem is .js file editor from ChomeDevTools should be used to create
breakpoints, because breakpoint annotation id used in mapping is different from breakpoint
annotation id used in JSDT.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)