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

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBDS-3896:
-----------------------------------

[~snjeza]  Can you make a new patch to JBDS that sets this preference by default?  I don't think this patch to jbt is appropriate, and previous discussion on mailing list 

> Unable to install breakpoint even if line number set to be generated
> --------------------------------------------------------------------
>
>                 Key: JBDS-3896
>                 URL: https://issues.jboss.org/browse/JBDS-3896
>             Project: Red Hat Developer Studio (DevStudio)
>          Issue Type: Bug
>          Components: upstream
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>             Fix For: 10.0.0.Alpha3
>
>         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)