February 2017 - jbosstools-issues

[JBoss JIRA] (ERT-480) JSDT stops breakpoints from working in C/C++ editors when CDT is installed [EBZ#511114]

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/ERT-480?page=com.atlassian.jira.plugin.sy... ] Victor Rubezhny updated ERT-480: -------------------------------- Story Points: 10 > JSDT stops breakpoints from working in C/C++ editors when CDT is installed [EBZ#511114] > --------------------------------------------------------------------------------------- > > Key: ERT-480 > URL: https://issues.jboss.org/browse/ERT-480 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Labels: Debug, bzira > > If you install CDT into an Eclipse containing Webtools or vice-versa then breakpoints stop working out-of-the-box in C/C++ code editors. > Reproduction steps: > 1. Download JEE distribution: eclipse-jee-neon-2-linux-gtk-x86_64.tar.gz > 2. Add the Neon CDT update site: http://download.eclipse.org/tools/cdt/releases/9.2 and install all "Main" and "Optional" features > 3. Create a new C project --> "Hello World ANSI C Project" > 4. Try to add breakpoint anywhere in the C file editor: (CTRL+SHIFT+B or from the main menu) > 5. Notice you can't add a C breakpoint > Workaround: > 1. Instead you have to switch breakpoint types by going to "Run" menu --> "Breakpoint Types" --> "C/C++ Breakpoints" > 2. Breakpoints can now be added as normal and as expected > I don't expect the default breakpoint type to be incorrect for C/C++ editors when I have JSDT installed. This only fails when CDT and JSDT are installed at the same time. > Quick brain dump of my understanding of the problem so far: > 1. There is a kind of JavaScript breakpoint adaptor factory registered by webtools JSDT that is too unrestricted in the kinds of editors to which it applies. It applies itself to all text editors, regardless of content and then at a later point checks the extension of the file open in the editor (this is at odds other implementations I've looked at, which register themselves for specific editor types.) > 2. The Eclipse debugging framework may be a bit sloppy checking whether a breakpoint adaptor exists for a given adaptable -- from reading the code, the adaptor manager method that is used seems to only go as far as checking to see if there is an adaptor factory available instead actually attempting to get an adaptor from the factory. This is problematic because the factory available for all editors, but it only returns an adaptor conditionally on the extension of the open file. This may be misleading the "toggle breakpoint" action into thinking it can apply a JavaScript breakpoint when it actually can't. > I will attach a patch that that restricts the problematic breakpoint adaptor factory to javascript editors. This fixes the problem for my use-case above. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23667) Tracking jira for moving reddeer wrapper plugins from integration-tests into component repo

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23667?page=com.atlassian.jira.plugi... ] Pavol Srna resolved JBIDE-23667. -------------------------------- Resolution: Done All plugins planned as part of this tracking jira have been moved to component repositories. Thus resolving. There are still other plugins left to be moved (batch.reddeer, hibernate.reddeer, forge.reddeer). Separate jiras will follow for better planning in agile board (since you cannot plan subtasks in jira as part of the agile board). > Tracking jira for moving reddeer wrapper plugins from integration-tests into component repo > ------------------------------------------------------------------------------------------- > > Key: JBIDE-23667 > URL: https://issues.jboss.org/browse/JBIDE-23667 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, openshift > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.4.3.AM2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23667) Tracking jira for moving reddeer wrapper plugins from integration-tests into component repo - Stage 1

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23667?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-23667: ------------------------------- Summary: Tracking jira for moving reddeer wrapper plugins from integration-tests into component repo - Stage 1 (was: Tracking jira for moving reddeer wrapper plugins from integration-tests into component repo) > Tracking jira for moving reddeer wrapper plugins from integration-tests into component repo - Stage 1 > ----------------------------------------------------------------------------------------------------- > > Key: JBIDE-23667 > URL: https://issues.jboss.org/browse/JBIDE-23667 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, openshift > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.4.3.AM2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-480) JSDT stops breakpoints from working in C/C++ editors when CDT is installed [EBZ#511114]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-480: --------------------------------------- Summary: JSDT stops breakpoints from working in C/C++ editors when CDT is installed [EBZ#511114] Key: ERT-480 URL: https://issues.jboss.org/browse/ERT-480 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Friendly Jira Robot If you install CDT into an Eclipse containing Webtools or vice-versa then breakpoints stop working out-of-the-box in C/C++ code editors. Reproduction steps: 1. Download JEE distribution: eclipse-jee-neon-2-linux-gtk-x86_64.tar.gz 2. Add the Neon CDT update site: http://download.eclipse.org/tools/cdt/releases/9.2 and install all "Main" and "Optional" features 3. Create a new C project --> "Hello World ANSI C Project" 4. Try to add breakpoint anywhere in the C file editor: (CTRL+SHIFT+B or from the main menu) 5. Notice you can't add a C breakpoint Workaround: 1. Instead you have to switch breakpoint types by going to "Run" menu --> "Breakpoint Types" --> "C/C++ Breakpoints" 2. Breakpoints can now be added as normal and as expected I don't expect the default breakpoint type to be incorrect for C/C++ editors when I have JSDT installed. This only fails when CDT and JSDT are installed at the same time. Quick brain dump of my understanding of the problem so far: 1. There is a kind of JavaScript breakpoint adaptor factory registered by webtools JSDT that is too unrestricted in the kinds of editors to which it applies. It applies itself to all text editors, regardless of content and then at a later point checks the extension of the file open in the editor (this is at odds other implementations I've looked at, which register themselves for specific editor types.) 2. The Eclipse debugging framework may be a bit sloppy checking whether a breakpoint adaptor exists for a given adaptable -- from reading the code, the adaptor manager method that is used seems to only go as far as checking to see if there is an adaptor factory available instead actually attempting to get an adaptor from the factory. This is problematic because the factory available for all editors, but it only returns an adaptor conditionally on the extension of the open file. This may be misleading the "toggle breakpoint" action into thinking it can apply a JavaScript breakpoint when it actually can't. I will attach a patch that that restricts the problematic breakpoint adaptor factory to javascript editors. This fixes the problem for my use-case above. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23321) Integration tests for OpenShift Node.js debugger

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23321?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-23321: ------------------------------- Fix Version/s: 4.4.3.Final (was: 4.4.3.AM2) > Integration tests for OpenShift Node.js debugger > ------------------------------------------------- > > Key: JBIDE-23321 > URL: https://issues.jboss.org/browse/JBIDE-23321 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: javascript, openshift > Affects Versions: 4.4.2.AM1 > Reporter: Ilya Buziuk > Assignee: Pavol Srna > Fix For: 4.4.3.Final > > > Node.js Debugging support implemented as part of https://issues.jboss.org/browse/JBIDE-22225 > Should be covered with red deer integration tests. Basically, test coverage of Node.js Debugger facilities already covered with red deer in JSDT project - https://git.eclipse.org/r/#/c/82836/ > However, implementing smth. similar for OpenShift will be much trickier. Basically, there is an integration test *org.jboss.tools.openshift.ui.bot.test.application.v3.adapter.PublishChangesTest* which is used for server adapter publishing. For now this test is not sustainable due to https://issues.jboss.org/browse/JBIDE-23005 . -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23740) For JBIDE 4.4.3.AM2: Prepare for 4.4.3.AM2 / 10.3.0.AM2 [arquillian]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23740?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-23740. ------------------------------ Resolution: Done Closing done. > For JBIDE 4.4.3.AM2: Prepare for 4.4.3.AM2 / 10.3.0.AM2 [arquillian] > -------------------------------------------------------------------- > > Key: JBIDE-23740 > URL: https://issues.jboss.org/browse/JBIDE-23740 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: arquillian > Reporter: Friendly Jira Robot > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.4.3.AM2 > > > For JBIDE 4.4.3.AM2 [arquillian]: Please perform the following tasks: 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.3.AM2-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.3.AM2-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: README.md features plugins pom.xml pom.xml.orig site tests *{color:orange}4.4.3.AM2-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. {code} mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT {code} 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for arquillian task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23746) For JBIDE 4.4.3.AM2: Prepare for 4.4.3.AM2 / 10.3.0.AM2 [hibernate]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23746?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-23746. ------------------------------ Resolution: Done Closing done. > For JBIDE 4.4.3.AM2: Prepare for 4.4.3.AM2 / 10.3.0.AM2 [hibernate] > ------------------------------------------------------------------- > > Key: JBIDE-23746 > URL: https://issues.jboss.org/browse/JBIDE-23746 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Reporter: Friendly Jira Robot > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.4.3.AM2 > > > For JBIDE 4.4.3.AM2 [hibernate]: Please perform the following tasks: 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.3.AM2-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.3.AM2-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: README.md dependencies.psf docs features plugins pom.xml pom.xml.orig sampleprojects site tests *{color:orange}4.4.3.AM2-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. {code} mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT {code} 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for hibernate task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23739) For JBIDE 4.4.3.AM2: Prepare for 4.4.3.AM2 / 10.3.0.AM2 [aerogear-hybrid]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23739?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-23739. ------------------------------ Resolution: Done Closing done. > For JBIDE 4.4.3.AM2: Prepare for 4.4.3.AM2 / 10.3.0.AM2 [aerogear-hybrid] > ------------------------------------------------------------------------- > > Key: JBIDE-23739 > URL: https://issues.jboss.org/browse/JBIDE-23739 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: aerogear-hybrid > Reporter: Friendly Jira Robot > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.4.3.AM2 > > > For JBIDE 4.4.3.AM2 [aerogear-hybrid]: Please perform the following tasks: 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.3.AM2-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.3.AM2-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: README.md all-tests cordova cordovasim feedhenry pom.xml pom.xml.orig site *{color:orange}4.4.3.AM2-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. {code} mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT {code} 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for aerogear-hybrid task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23745) For JBIDE 4.4.3.AM2: Prepare for 4.4.3.AM2 / 10.3.0.AM2 [freemarker]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23745?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-23745. ------------------------------ Resolution: Done Closing done. > For JBIDE 4.4.3.AM2: Prepare for 4.4.3.AM2 / 10.3.0.AM2 [freemarker] > -------------------------------------------------------------------- > > Key: JBIDE-23745 > URL: https://issues.jboss.org/browse/JBIDE-23745 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: freemarker > Reporter: Friendly Jira Robot > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.4.3.AM2 > > > For JBIDE 4.4.3.AM2 [freemarker]: Please perform the following tasks: 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.3.AM2-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.3.AM2-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: README.md features plugins pom.xml pom.xml.orig site tests *{color:orange}4.4.3.AM2-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. {code} mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT {code} 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for freemarker task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23754) For JBIDE 4.4.3.AM2: Prepare for 4.4.3.AM2 / 10.3.0.AM2 [integration-tests]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23754?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-23754. ------------------------------ Resolution: Done Closing done. > For JBIDE 4.4.3.AM2: Prepare for 4.4.3.AM2 / 10.3.0.AM2 [integration-tests] > --------------------------------------------------------------------------- > > Key: JBIDE-23754 > URL: https://issues.jboss.org/browse/JBIDE-23754 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests > Reporter: Friendly Jira Robot > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.4.3.AM2 > > > For JBIDE 4.4.3.AM2 [integration-tests]: Please perform the following tasks: 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.3.AM2-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.3.AM2-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: README.md plugins pom.xml pom.xml.orig site tests *{color:orange}4.4.3.AM2-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. {code} mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT {code} 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for integration-tests task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues February 2017