August 2019 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26800) Update 4.13.0.AM1 Target Platform (Docker tooling, ...) for 2019-09.M3

by stephane bouchet (Jira)

[ https://issues.jboss.org/browse/JBIDE-26800?page=com.atlassian.jira.plugi... ] stephane bouchet updated JBIDE-26800: ------------------------------------- Git Pull Request: (was: https://github.com/jbosstools/jbosstools-target-platforms/pull/329) > Update 4.13.0.AM1 Target Platform (Docker tooling, ...) for 2019-09.M3 > ---------------------------------------------------------------------- > > Key: JBIDE-26800 > URL: https://issues.jboss.org/browse/JBIDE-26800 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.13.0.AM1 > Reporter: Jeff MAURY > Assignee: stephane bouchet > Priority: Major > Fix For: 4.13.0.AM1 > > -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26795) Investigate removal of swtbot from target platform

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26795?page=com.atlassian.jira.plugi... ] André Dietisheim updated JBIDE-26795: ------------------------------------- Fix Version/s: 4.13.x > Investigate removal of swtbot from target platform > -------------------------------------------------- > > Key: JBIDE-26795 > URL: https://issues.jboss.org/browse/JBIDE-26795 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.13.0.AM1 > Reporter: stephane bouchet > Priority: Minor > Fix For: 4.13.x > > > While updating to 2019-09, i discussed with [~odockal] about updating swtbot to a newer version, and it ends with a removal proposition as swtbot is already taken care of by the reddeer project. > This task is about discussing/investigating the proper removal of swtbot as direct dependency in the jbosstools Target Platform. -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26795) Investigate removal of swtbot from target platform

by stephane bouchet (Jira)

[ https://issues.jboss.org/browse/JBIDE-26795?page=com.atlassian.jira.plugi... ] stephane bouchet commented on JBIDE-26795: ------------------------------------------ tested to remove swtbot from the current tp and got an error while validating : {code} [ERROR] Resolution failed: [ERROR] Software being installed: org.eclipse.linuxtools.docker.tests.feature.feature.group 4.4.0.201908091806 [ERROR] Missing requirement: org.eclipse.linuxtools.docker.ui.tests 2.2.0.201908091806 requires 'osgi.bundle; org.eclipse.swtbot.junit4_x 2.3.0' but it could not be found [ERROR] Cannot satisfy dependency: org.eclipse.linuxtools.docker.tests.feature.feature.group 4.4.0.201908091806 depends on: org.eclipse.equinox.p2.iu; org.eclipse.linuxtools.docker.ui.tests [2.2.0.201908091806,2.2.0.201908091806] {code} so i think no removal is needed for now. > Investigate removal of swtbot from target platform > -------------------------------------------------- > > Key: JBIDE-26795 > URL: https://issues.jboss.org/browse/JBIDE-26795 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.13.0.AM1 > Reporter: stephane bouchet > Priority: Minor > > While updating to 2019-09, i discussed with [~odockal] about updating swtbot to a newer version, and it ends with a removal proposition as swtbot is already taken care of by the reddeer project. > This task is about discussing/investigating the proper removal of swtbot as direct dependency in the jbosstools Target Platform. -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-766) Add test for Access Pattern export in dynamic VDB (TEIIDDES-2788)

by Matus Makovy (Jira)

[ https://issues.jboss.org/browse/JBTIS-766?page=com.atlassian.jira.plugin.... ] Matus Makovy closed JBTIS-766. ------------------------------ Resolution: Out of Date > Add test for Access Pattern export in dynamic VDB (TEIIDDES-2788) > ------------------------------------------------------------------ > > Key: JBTIS-766 > URL: https://issues.jboss.org/browse/JBTIS-766 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: QE, teiid > Affects Versions: 4.3.0.Final > Reporter: Matus Makovy > Assignee: Matus Makovy > Priority: Major > Fix For: 4.3.1.Final > > -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26718) Fix builds for TP based on 2019-09.M2

by stephane bouchet (Jira)

[ https://issues.jboss.org/browse/JBIDE-26718?page=com.atlassian.jira.plugi... ] stephane bouchet commented on JBIDE-26718: ------------------------------------------ I think we're good now. > Fix builds for TP based on 2019-09.M2 > ------------------------------------- > > Key: JBIDE-26718 > URL: https://issues.jboss.org/browse/JBIDE-26718 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.13.0.AM1 > Reporter: Jeff MAURY > Assignee: stephane bouchet > Priority: Major > Fix For: 4.13.0.AM1 > > -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4789) Disable "show method result after a step operation" by default

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBDS-4789?page=com.atlassian.jira.plugin.... ] André Dietisheim commented on JBDS-4789: ---------------------------------------- If Eclipse decides to disable this preference by default (see https://bugs.eclipse.org/bugs/show_bug.cgi?id=533702#c7) we'll have to remove this change in CRStudio. > Disable "show method result after a step operation" by default > -------------------------------------------------------------- > > Key: JBDS-4789 > URL: https://issues.jboss.org/browse/JBDS-4789 > Project: Red Hat CodeReady Studio (devstudio) > Issue Type: Enhancement > Components: product > Affects Versions: 12.13.0.AM1 > Reporter: André Dietisheim > Assignee: André Dietisheim > Priority: Major > Attachments: show-method-result-after-step-operation.png > > > Stepping over code while debugging is very very slow in current Eclipse. Turns out that this is due to a preference setting that is enabled by default: > *show method result after a step operation* > !show-method-result-after-step-operation.png! > We thus should consider turning this off by default in CRStudio. > The issue is being reported/discussed in Eclipse bugs at https://bugs.eclipse.org/bugs/show_bug.cgi?id=533702 and https://bugs.eclipse.org/bugs/show_bug.cgi?id=536751 where a slowdown of 10x is reported. Eclipse thus is considering turning it off by default: https://bugs.eclipse.org/bugs/show_bug.cgi?id=533702#c7 > This is especially painful when remote debugging applications in OpenShift: JBIDE-26794 -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26794) OpenShift: Remote debugging is very slow

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26794?page=com.atlassian.jira.plugi... ] André Dietisheim edited comment on JBIDE-26794 at 8/27/19 11:41 AM: -------------------------------------------------------------------- we are apparently able to set the default for this preference setting in CRStudio. Reopening to create a PR: JBDS-4789 was (Author: adietish): we are apparently able to set the default for this preference setting in CRStudio. Reopening to create a PR. > OpenShift: Remote debugging is very slow > ---------------------------------------- > > Key: JBIDE-26794 > URL: https://issues.jboss.org/browse/JBIDE-26794 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.11.0.Final > Environment: Version: 12.11.0.GA > Build id: GA-v20190329-0120-B4247 > Build date: 20190329-0120 > RHPDS > Reporter: Josef Kopriva > Assignee: André Dietisheim > Priority: Major > Labels: debugging > Fix For: 4.13.0.AM1 > > Attachments: disable-show-method-result.png > > > From Email on devtools-team from [~jgammonred612]: > {code:java} > Hi Folks: > Using this version of Code Ready Studio > Version: 12.11.0.GA > Build id: GA-v20190329-0120-B4247 > Build date: 20190329-0120 > I recently ran an Openshift Starter Workshop lab and witnessed a clear > issue with Code Ready Studio and INtelliJ > Workshop Starter Lab > (http://starter-guides-labs.b9ad.pro-us-east-1.openshiftapps.com/workshop/...) > Lab 19 has a remote debugging setup. The remote debugger in Code Ready > connected very very slowly and would not step over or step out making > using it as a debugger virtually impossible. > One of the lab participants had IntelliJ and it connected immediately > and worked just fine. > Clearly, something is broken in CRS. Maybe someone would want to test > this out and fix? > You can find this lab on RHPDS. > Just FYI to the PM's. > {code} -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4789) Disable "show method result after a step operation" by default

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBDS-4789?page=com.atlassian.jira.plugin.... ] André Dietisheim updated JBDS-4789: ----------------------------------- Description: Stepping over code while debugging is very very slow in current Eclipse. Turns out that this is due to a preference setting that is enabled by default: *show method result after a step operation* !show-method-result-after-step-operation.png! We thus should consider turning this off by default in CRStudio. The issue is being reported/discussed in Eclipse bugs at https://bugs.eclipse.org/bugs/show_bug.cgi?id=533702 and https://bugs.eclipse.org/bugs/show_bug.cgi?id=536751 where a slowdown of 10x is reported. Eclipse thus is considering turning it off by default: https://bugs.eclipse.org/bugs/show_bug.cgi?id=533702#c7 This is especially painful when remote debugging applications in OpenShift: JBIDE-26794 was: Stepping over code while debugging is very very slow in current Eclipse. Turns out that this is due to a preference setting that is enabled by default: *show method result after a step operation* !show-method-result-after-step-operation.png! We thus should consider turning this off by default in CRStudio. The is being reported in Eclipse bugs at https://bugs.eclipse.org/bugs/show_bug.cgi?id=533702 and https://bugs.eclipse.org/bugs/show_bug.cgi?id=536751 where a slowdown of 10x is reported. Eclipse thus is considering turning it off by default: https://bugs.eclipse.org/bugs/show_bug.cgi?id=533702#c7 This is especially painful when remote debugging applications in OpenShift: JBIDE-26794 > Disable "show method result after a step operation" by default > -------------------------------------------------------------- > > Key: JBDS-4789 > URL: https://issues.jboss.org/browse/JBDS-4789 > Project: Red Hat CodeReady Studio (devstudio) > Issue Type: Enhancement > Components: product > Affects Versions: 12.13.0.AM1 > Reporter: André Dietisheim > Assignee: André Dietisheim > Priority: Major > Attachments: show-method-result-after-step-operation.png > > > Stepping over code while debugging is very very slow in current Eclipse. Turns out that this is due to a preference setting that is enabled by default: > *show method result after a step operation* > !show-method-result-after-step-operation.png! > We thus should consider turning this off by default in CRStudio. > The issue is being reported/discussed in Eclipse bugs at https://bugs.eclipse.org/bugs/show_bug.cgi?id=533702 and https://bugs.eclipse.org/bugs/show_bug.cgi?id=536751 where a slowdown of 10x is reported. Eclipse thus is considering turning it off by default: https://bugs.eclipse.org/bugs/show_bug.cgi?id=533702#c7 > This is especially painful when remote debugging applications in OpenShift: JBIDE-26794 -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4789) Disable "show method result after a step operation" by default

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBDS-4789?page=com.atlassian.jira.plugin.... ] André Dietisheim updated JBDS-4789: ----------------------------------- Description: Stepping over code while debugging is very very slow in current Eclipse. Turns out that this is due to a preference setting that is enabled by default: *show method result after a step operation* !show-method-result-after-step-operation.png! We thus should consider turning this off by default in CRStudio. The is being reported in Eclipse bugs at https://bugs.eclipse.org/bugs/show_bug.cgi?id=533702 and https://bugs.eclipse.org/bugs/show_bug.cgi?id=536751 where a slowdown of 10x is reported. Eclipse thus is considering turning it off by default: https://bugs.eclipse.org/bugs/show_bug.cgi?id=533702#c7 This is especially painful when remote debugging applications in OpenShift: JBIDE-26794 was: Stepping over code while debugging is very very slow in current Eclipse. Turns out that this is due to a preference setting that is enabled by default: *show method result after a step operation* We thus should consider turning this off by default in CRStudio. The is being reported in Eclipse bugs at https://bugs.eclipse.org/bugs/show_bug.cgi?id=533702 and https://bugs.eclipse.org/bugs/show_bug.cgi?id=536751 where a slowdown of 10x is reported. Eclipse thus is considering turning it off by default: https://bugs.eclipse.org/bugs/show_bug.cgi?id=533702#c7 This is especially painful when remote debugging applications in OpenShift: JBIDE-26794 > Disable "show method result after a step operation" by default > -------------------------------------------------------------- > > Key: JBDS-4789 > URL: https://issues.jboss.org/browse/JBDS-4789 > Project: Red Hat CodeReady Studio (devstudio) > Issue Type: Enhancement > Components: product > Affects Versions: 12.13.0.AM1 > Reporter: André Dietisheim > Assignee: André Dietisheim > Priority: Major > Attachments: show-method-result-after-step-operation.png > > > Stepping over code while debugging is very very slow in current Eclipse. Turns out that this is due to a preference setting that is enabled by default: > *show method result after a step operation* > !show-method-result-after-step-operation.png! > We thus should consider turning this off by default in CRStudio. > The is being reported in Eclipse bugs at https://bugs.eclipse.org/bugs/show_bug.cgi?id=533702 and https://bugs.eclipse.org/bugs/show_bug.cgi?id=536751 where a slowdown of 10x is reported. Eclipse thus is considering turning it off by default: https://bugs.eclipse.org/bugs/show_bug.cgi?id=533702#c7 > This is especially painful when remote debugging applications in OpenShift: JBIDE-26794 -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4789) Disable "show method result after a step operation" by default

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBDS-4789?page=com.atlassian.jira.plugin.... ] André Dietisheim updated JBDS-4789: ----------------------------------- Attachment: show-method-result-after-step-operation.png > Disable "show method result after a step operation" by default > -------------------------------------------------------------- > > Key: JBDS-4789 > URL: https://issues.jboss.org/browse/JBDS-4789 > Project: Red Hat CodeReady Studio (devstudio) > Issue Type: Enhancement > Components: product > Affects Versions: 12.13.0.AM1 > Reporter: André Dietisheim > Assignee: André Dietisheim > Priority: Major > Attachments: show-method-result-after-step-operation.png > > > Stepping over code while debugging is very very slow in current Eclipse. Turns out that this is due to a preference setting that is enabled by default: > *show method result after a step operation* > We thus should consider turning this off by default in CRStudio. > The is being reported in Eclipse bugs at https://bugs.eclipse.org/bugs/show_bug.cgi?id=533702 and https://bugs.eclipse.org/bugs/show_bug.cgi?id=536751 where a slowdown of 10x is reported. Eclipse thus is considering turning it off by default: https://bugs.eclipse.org/bugs/show_bug.cgi?id=533702#c7 > This is especially painful when remote debugging applications in OpenShift: JBIDE-26794 -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2019