[JBoss JIRA] (JBIDE-20845) Unable to install breakpoint even if line number set to be generated
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20845?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-20845:
---------------------------------------
See http://screencast.com/t/vNYWg1Bps
> 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, 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)
9 years, 1 month
[JBoss JIRA] (JBIDE-21035) Build with Tycho 0.24.0
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21035?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-21035:
----------------------------------
Assignee: Nick Boldt
> Build with Tycho 0.24.0
> -----------------------
>
> Key: JBIDE-21035
> URL: https://issues.jboss.org/browse/JBIDE-21035
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> {quote}
> Tycho milestone 0.24.0 has been released and is available from maven central.
> See the release notes [1] for details of enhancements and bug fixes in this release.
> Thanks to:
> Alexander Kurtakov
> Lars Vogel
> Mickael Istria
> Mikolaj Izdebski
> who contributed patches for this release.
> And thanks and to everyone who helped us with testing the staged version.
> Regards,
> Tycho team
> [1] http://wiki.eclipse.org/Tycho/Release_Notes/0.24
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (JBIDE-21035) Build with Tycho 0.24.0
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21035?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-21035:
-------------------------------
Fix Version/s: 4.3.1.Beta1
4.4.0.Alpha1
> Build with Tycho 0.24.0
> -----------------------
>
> Key: JBIDE-21035
> URL: https://issues.jboss.org/browse/JBIDE-21035
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> {quote}
> Tycho milestone 0.24.0 has been released and is available from maven central.
> See the release notes [1] for details of enhancements and bug fixes in this release.
> Thanks to:
> Alexander Kurtakov
> Lars Vogel
> Mickael Istria
> Mikolaj Izdebski
> who contributed patches for this release.
> And thanks and to everyone who helped us with testing the staged version.
> Regards,
> Tycho team
> [1] http://wiki.eclipse.org/Tycho/Release_Notes/0.24
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (JBIDE-21035) Build with Tycho 0.24.0
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-21035:
----------------------------------
Summary: Build with Tycho 0.24.0
Key: JBIDE-21035
URL: https://issues.jboss.org/browse/JBIDE-21035
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1
Reporter: Nick Boldt
{quote}
Tycho milestone 0.24.0 has been released and is available from maven central.
See the release notes [1] for details of enhancements and bug fixes in this release.
Thanks to:
Alexander Kurtakov
Lars Vogel
Mickael Istria
Mikolaj Izdebski
who contributed patches for this release.
And thanks and to everyone who helped us with testing the staged version.
Regards,
Tycho team
[1] http://wiki.eclipse.org/Tycho/Release_Notes/0.24
{quote}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (JBIDE-20845) Unable to install breakpoint even if line number set to be generated
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20845?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-20845:
---------------------------------------
{quote}
1. Why does it display the warning in the first place? It seems that the breakpoint works fine, so why is Eclipse complaining (unless you make turn off the warning)?
{quote}
Eclipse sets that by default.
{quote}
2. Why do I need to click the "List Members" button in the web app to trigger this when Vlado Pakan allegedly didn't have to do that. Now I actually tend to think that Vlado must have had the breakpoint somewhere else, because it seems to make sense to me that the listAllMembers method is only called when you want to list the members.
{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?
> 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, 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)
9 years, 1 month
[JBoss JIRA] (JBIDE-20923) Wrong archetype is picked for unreleased EAP (7)
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20923?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-20923:
--------------------------------
Fix Version/s: 4.3.1.Beta1
> Wrong archetype is picked for unreleased EAP (7)
> ------------------------------------------------
>
> Key: JBIDE-20923
> URL: https://issues.jboss.org/browse/JBIDE-20923
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.3.0.Final
> Reporter: Radim Hopp
> Assignee: Fred Bricon
> Fix For: 4.3.1.Beta1
>
>
> When EAP 7 is selected as target runtime when creating project from archetype (EAR Project for example), version org.jboss.spec.archetypes:jboss-javaee6-webapp-ear-archetype:7.1.3.Final is selected (JBoss AS 7.1 archetype).
> Instead of this, either last released EAP version (currently 6.4) archetype should be selected, or the "most compatible" (at this time probably WFLY 8.2 archetype)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (JBIDE-20923) Wrong archetype is picked for unreleased EAP (7)
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20923?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-20923:
-----------------------------------
Assignee: Fred Bricon
> Wrong archetype is picked for unreleased EAP (7)
> ------------------------------------------------
>
> Key: JBIDE-20923
> URL: https://issues.jboss.org/browse/JBIDE-20923
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.3.0.Final
> Reporter: Radim Hopp
> Assignee: Fred Bricon
>
> When EAP 7 is selected as target runtime when creating project from archetype (EAR Project for example), version org.jboss.spec.archetypes:jboss-javaee6-webapp-ear-archetype:7.1.3.Final is selected (JBoss AS 7.1 archetype).
> Instead of this, either last released EAP version (currently 6.4) archetype should be selected, or the "most compatible" (at this time probably WFLY 8.2 archetype)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month