[
https://issues.jboss.org/browse/JBIDE-20845?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-20845:
---------------------------------------
It doesn't do anything, but it turns out in my case I needed to click the List Members
button in the web app to trigger the breakpoint - so eventually it worked even despite
this error. But for Vlado (Fedora 22, KDE) it worked right away - no Line Number error and
no need to click any button in the web app. (But as I said earlier, Pavol hit the same
issue as me on Linux.) So something is odd here. But at least I was now able to verify
that the source lookup but is fixed.
Unable to install breakpoint even if line number set to be generated
--------------------------------------------------------------------
Key: JBIDE-20845
URL:
https://issues.jboss.org/browse/JBIDE-20845
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: upstream
Affects Versions: 4.3.0.CR2
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.3.1.Final, 4.4.0.Alpha1
Attachments: breakpoint-error.png, compiler-settings.png
I am unable to get breakpoints to work for a html5 project running on WildFly.
I tried to verify JBIDE-20804 so I created the html5 project from central, set a
breakpoint in MemberService.listAllMembers() (line 72) and then selected Debug on server
-> WildFly. The server was started in debugging mode and the project started deploying,
but then I got an error:
Unable to install breakpoint in org.jboss.tools.example.html5.rest.MemberService$$$view3
due to missing line number attributes. Modify compiler options to generate line number
attributes.
Reason: Absent Line Number Information
!breakpoint-error.png!
I checked and this option was checked in Preferences -> Java -> Compiler. Also, I
even checked the project settings (.settings/org.eclipse.jdt.core.prefs) and it has:
org.eclipse.jdt.core.compiler.debug.lineNumber=generate
This happened to me on Mac with WildFly 8, 9 and 10. And psrna checked this for me on
Linux and the result was the same.
I'm not really sure which component this should belong to, it looks like an upstream
issue.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)