[jbosstools-issues] [JBoss JIRA] (JBIDE-20845) Unable to install breakpoint even if line number set to be generated

Martin Malina (JIRA) issues at jboss.org
Fri Nov 13 07:30:00 EST 2015


    [ https://issues.jboss.org/browse/JBIDE-20845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13128702#comment-13128702 ] 

Martin Malina edited comment on JBIDE-20845 at 11/13/15 7:29 AM:
-----------------------------------------------------------------

{quote}
Eclipse sets that by default.
{quote}

I understand that by default the warning is shown, but only if Eclipse thinks it cannot see the line number attributes. And I have that enabled. So that's what I meant to ask: Why is Eclipse showing this warning even if everything should work and seems to work - it seems that showing the warning is simply wrong in this case.

{quote}
I have set a breakpoint to MemberService.listAllMembers() (line 72).
I don't have to click the "List Members" button no matter whether the "Warn when unable to install breakpoint..." checkbox is checked or not.
Could you try again in a new workspace?
{quote}
I saw your screencast and I believed you even without it :) But still, in my case the breakpoint is only hit if I click the button on the web page. And now I can see why. For some reason I always get the mobile version of the page, so the list of members isn't shown and the breakpoint isn't triggered.

!html5-page.png!


was (Author: mmalina):
{quote}
Eclipse sets that by default.
{quote}

I understand that by default the warning is shown, but only if Eclipse thinks it cannot see the line number attributes. And I have that enabled. So that's what I meant to ask: Why is Eclipse showing this warning even if everything should work and seems to work - it seems that showing the warning is simply wrong in this case.

{quote}
I have set a breakpoint to MemberService.listAllMembers() (line 72).
I don't have to click the "List Members" button no matter whether the "Warn when unable to install breakpoint..." checkbox is checked or not.
Could you try again in a new workspace?
{quote}
I saw your screencast and I believed you even without it :) But still, in my case the breakpoint is only hit if I click the button on the web page. And now I can see why. For some reason I always get the mobile version of the page, so the list of members isn't shown and the breakpoint isn't triggered.


> 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.x, 4.4.0.Alpha1
>
>         Attachments: breakpoint-error.png, compiler-settings.png, html5-page.png, lineNumber.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)


More information about the jbosstools-issues mailing list