October 2015 - jbosstools-issues - Jboss List Archives

[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)

10 years

1
0
0 / 0

[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)

10 years

1
0
0 / 0

[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)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-20842) Need to implement npm support

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20842?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-20842: ------------------------------------- PR was sent - https://github.com/jbosstools/jbosstools-jst/pull/549 - "npm Init" New wizard for package.json creation - "npm Update" & "npm Install" launch shortcuts - Initial SWTBot tests (org.jboss.tools.jst.js.node.test plugin) > Need to implement npm support > ----------------------------- > > Key: JBIDE-20842 > URL: https://issues.jboss.org/browse/JBIDE-20842 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript > Affects Versions: 4.3.0.CR1 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: new_and_noteworthy > Fix For: 4.4.0.Alpha1 > > > Initially npm support should include the following commands: > 1) [init|https://docs.npmjs.com/cli/init] - package.json creation > 2) [update|https://docs.npmjs.com/cli/update] - updates all the packages listed to the latest version > 3) [install|https://docs.npmjs.com/cli/install] (no arguments) - Installs the dependencies in the local *node_modules* folder -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

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

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20845?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-20845: --------------------------------------- [~snjeza], I tried again now. And you are right, when I uncheck "Warn when unable to install breakpoint...", it will no longer complain and when I click "List Members" in the web app, it will hit the breakpoint. But there are still a few questions: 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)? 2. Why do I need to click the "List Members" button in the web app to trigger this when [~vpakan] 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. > 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)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-20442) Create SWTBot integration tests for tern related features

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20442?page=com.atlassian.jira.plugi... ] Vlado Pakan commented on JBIDE-20442: ------------------------------------- Nothing from test scenarios above is implemented. I have test checking code assist for AngularJS attributes 'ng-*' but I don't know if that is coming from Tern > Create SWTBot integration tests for tern related features > --------------------------------------------------------- > > Key: JBIDE-20442 > URL: https://issues.jboss.org/browse/JBIDE-20442 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Critical > Fix For: 4.3.x > > > There should be set of SWTBot tests that would cover functionality related to tern.java and angularjs-eclipse integration. These tests would simplify migration to new tern.java and angularjs-eclipse releases. > Current process for migration to new version of tern-java/angularjs-eclipse is manual. Steps below describe current approach: > 1. Manual mirroring of latest tern-java/angularjs-eclipse versions to local filesystem; > 2. Build jbosstools-jst with local mirrors and run JUnit tests; > 3. Install latest tern-java and angularjs-eclipse form mirrors done in (1) into JBDS nightly build from master branch (it has open version range for tern features) and restart; > 4. Run manual tests; > 5. If (2) and (3) idenify no problems then local mirrors should be published to http://download.jboss.org/jbosstools/updates/requirements/tern and http://download.jboss.org/jbosstools/updates/requirements/angularjs respectively; > 6. Update jbosstools-jst with new versions for tern-java/angularjs-eclipse and push local branch to upstream > With step 4 implemented as SWT bot tests and automated mirroring for tern-java and angularjs-eclipse (see jenkins job here https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/All/job/jbosstools-...) we can fully automate the process above. > QA also can skip step (1) and just use external p2 repos: > * http://oss.opensagres.fr/tern.repository/1.0.0-SNAPSHOT/ > * http://oss.opensagres.fr/angularjs-eclipse/1.0.0-SNAPSHOT/ > in step (2) by building jbosstools-jst as: > {code}mvn clean install -Dtern.repo.url=http://oss.opensagres.fr/tern.repository/1.0.0-SNAPSHOT/ -Dhttp://oss.opensagres.fr/angularjs-eclipse/1.0.0-SNAPSHOT/{code} > and installing latest versions for step (3). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21034) new Runtime detector fails to use default (ext-pt) enablement if user has previouslymodified enablement list

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-21034: ----------------------------------- Summary: new Runtime detector fails to use default (ext-pt) enablement if user has previouslymodified enablement list Key: JBIDE-21034 URL: https://issues.jboss.org/browse/JBIDE-21034 Project: Tools (JBoss Tools) Issue Type: Bug Components: runtime-detection Affects Versions: 4.3.0.Final Reporter: Rob Stryker Small coding error causes a new runtime detector to not have its default enablement respected if a user has previously modified the enablement of any detector. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-20990) Add "CDK Server" for start/stop for the CDK

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20990?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20990: --------------------------------------------- [~burrsutter] btw. if we could avoid having different names for this thing in community vs product that would be great - i.e. its ADB in community and CDK in product. Would be good if we could have a common name to refer to it. > Add "CDK Server" for start/stop for the CDK > ------------------------------------------- > > Key: JBIDE-20990 > URL: https://issues.jboss.org/browse/JBIDE-20990 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > > We want to be able to start/stop CDK easily. > Current suggestion is to use a server entry in server view that can start/stop vagrant by simply knowing its file location would be a good start. > note: the vagrant image might already be running so just need to be able to take care of that. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21033) Add SmokeSuite to org.jboss.tools.mylyn.ui.bot.test

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21033?page=com.atlassian.jira.plugi... ] Len DiMaggio commented on JBIDE-21033: -------------------------------------- https://github.com/jbosstools/jbosstools-integration-tests/pull/1221 > Add SmokeSuite to org.jboss.tools.mylyn.ui.bot.test > --------------------------------------------------- > > Key: JBIDE-21033 > URL: https://issues.jboss.org/browse/JBIDE-21033 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.3.0.Final > Reporter: Len DiMaggio > Assignee: Len DiMaggio > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21033) Add SmokeSuite to org.jboss.tools.mylyn.ui.bot.test

by Len DiMaggio (JIRA)

Len DiMaggio created JBIDE-21033: ------------------------------------ Summary: Add SmokeSuite to org.jboss.tools.mylyn.ui.bot.test Key: JBIDE-21033 URL: https://issues.jboss.org/browse/JBIDE-21033 Project: Tools (JBoss Tools) Issue Type: Task Components: qa Affects Versions: 4.3.0.Final Reporter: Len DiMaggio -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2015