September 2019 - jbosstools-issues

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

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBDS-4789?page=com.atlassian.jira.plugin.... ] Jeff MAURY updated JBDS-4789: ----------------------------- Sprint: devex #172 Sep 2019, devex #171 Aug 2019 (was: devex #171 Aug 2019) > 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: openshift, product > Affects Versions: 12.13.0.AM1 > Reporter: André Dietisheim > Assignee: André Dietisheim > Priority: Major > Fix For: 12.13.0.AM1 > > 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)

4 years, 9 months

1
0
0 / 0

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

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26800?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26800: ------------------------------- Sprint: devex #172 Sep 2019, devex #171 Aug 2019 (was: devex #171 Aug 2019) > 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 > > Attachments: p2diff_log_jbosstools_2019-09-03_14-46.txt > > -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26802) Warn users of the server adapter if "show method result" pref is enabled

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26802?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26802: ------------------------------- Sprint: devex #172 Sep 2019, devex #171 Aug 2019 (was: devex #171 Aug 2019) > Warn users of the server adapter if "show method result" pref is enabled > ------------------------------------------------------------------------ > > Key: JBIDE-26802 > URL: https://issues.jboss.org/browse/JBIDE-26802 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.13.0.AM1 > Reporter: André Dietisheim > Assignee: André Dietisheim > Priority: Major > Labels: debug-options, server_adapter > Fix For: 4.13.0.AM1 > > Attachments: show-method-result-after-step-operation.png > > > In JBIDE-26794 it turned out that when the preference value "show method result" is turned on, stepping over code that runs in OpenShift is slow to the point of being unusable. > !show-method-result-after-step-operation.png! > The cause for this slowness - the pref value mentioned above - is completely non-obvious to non-savvy users. We thus should warn users and allow them to disable it if the detect it. -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23666) Update or remove quickstarts on Central Home Page

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-23666?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23666: ------------------------------- Sprint: devex #169 July 2019, devex #172 Sep 2019, devex #171 Aug 2019 (was: devex #169 July 2019, devex #171 Aug 2019) > Update or remove quickstarts on Central Home Page > ------------------------------------------------- > > Key: JBIDE-23666 > URL: https://issues.jboss.org/browse/JBIDE-23666 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.4.3.AM1 > Environment: Red Hat JBoss Developer Studio > Version: 10.3.0.AM1 > Build id: AM1-v20161225-1238-B6761 > Build date: 20161225-1238 > Reporter: Josef Kopriva > Assignee: André Dietisheim > Priority: Critical > Fix For: 4.13.0.AM1 > > > Quickstarts on Central home page are old(links: "HTML5 Project", "AngularJS Forge", "Java EE Web Project"), so when importing these quickstarts, multiple warnings occur: > {code:java} > Description Resource Path Location Type > Build path specifies execution environment JavaSE-1.6. There are no JREs installed in the workspace that are strictly compatible with this environment. jboss-as-kitchensink-html5-mobile Build path JRE System Library Problem > Build path specifies execution environment JavaSE-1.7. There are no JREs installed in the workspace that are strictly compatible with this environment. jboss-forge-html5 Build path JRE System Library Problem > Build path specifies execution environment JavaSE-1.7. There are no JREs installed in the workspace that are strictly compatible with this environment. jboss-javaee-webapp Build path JRE System Library Problem > No connection specified for project. No database-specific validation will be performed. jboss-as-kitchensink-html5-mobile JPA Problem > No connection specified for project. No database-specific validation will be performed. jboss-forge-html5 JPA Problem > No connection specified for project. No database-specific validation will be performed. jboss-javaee-webapp JPA Problem > No grammar constraints (DTD or XML Schema) referenced in the document. cheatsheet.xml /jboss-forge-html5 line 1 XML Problem > No grammar constraints (DTD or XML Schema) referenced in the document. wro.xml /jboss-as-kitchensink-html5-mobile/src/main/webapp/WEB-INF line 1 XML Problem > {code} > For example HTML5 Project is downloading quickstart "jboss-as-kitchensink-html5-mobile", which is probably https://github.com/jboss-developer/jboss-wfk-quickstarts/tree/33c4600/kit... and this quickstart is requiring Java 1.6. This quickstart can be replaced with newer from https://github.com/jboss-developer/jboss-eap-quickstarts/tree/4aa3caa/kit... -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24899) Deploy Docker Image wizard: Image not found

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-24899?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24899: ------------------------------- Sprint: devex #169 July 2019, devex #172 Sep 2019, devex #171 Aug 2019 (was: devex #169 July 2019, devex #171 Aug 2019) > Deploy Docker Image wizard: Image not found > ------------------------------------------- > > Key: JBIDE-24899 > URL: https://issues.jboss.org/browse/JBIDE-24899 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, docker, openshift > Affects Versions: 4.5.1.AM1 > Reporter: Josef Kopriva > Assignee: André Dietisheim > Priority: Major > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.13.0.AM1 > > Attachments: image-2017-08-29-09-50-20-927.png > > > Exception in Error log: > {code:java} > Failed to inspect image: '172.30.1.1:5000/test/hola:latest' > com.spotify.docker.client.exceptions.ImageNotFoundException: Image not found: 172.30.1.1:5000/test/hola:latest > at com.spotify.docker.client.DefaultDockerClient.inspectImage(DefaultDockerClient.java:1330) > at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getImageInfo(DockerConnection.java:896) > at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImageWizardModel.lookupImageMetadata(DeployImageWizardModel.java:655) > at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImageWizardModel.initializeContainerInfo(DeployImageWizardModel.java:354) > at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImagePage$1ImageValidatorJob.run(DeployImagePage.java:154) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > Caused by: com.spotify.docker.client.exceptions.DockerRequestException: Request error: GET https://192.168.42.121:2376/images/172.30.1.1:5000/test/hola:latest/json: 404 > at com.spotify.docker.client.DefaultDockerClient.propagate(DefaultDockerClient.java:2084) > at com.spotify.docker.client.DefaultDockerClient.request(DefaultDockerClient.java:2023) > at com.spotify.docker.client.DefaultDockerClient.inspectImage(DefaultDockerClient.java:1326) > ... 5 more > Caused by: javax.ws.rs.NotFoundException: HTTP 404 Not Found > at org.glassfish.jersey.client.JerseyInvocation.convertToException(JerseyInvocation.java:1008) > at org.glassfish.jersey.client.JerseyInvocation.translate(JerseyInvocation.java:816) > at org.glassfish.jersey.client.JerseyInvocation.access$700(JerseyInvocation.java:92) > at org.glassfish.jersey.client.JerseyInvocation$5.completed(JerseyInvocation.java:773) > at org.glassfish.jersey.client.ClientRuntime.processResponse(ClientRuntime.java:198) > at org.glassfish.jersey.client.ClientRuntime.access$300(ClientRuntime.java:79) > at org.glassfish.jersey.client.ClientRuntime$2.run(ClientRuntime.java:180) > at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271) > at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267) > at org.glassfish.jersey.internal.Errors.process(Errors.java:315) > at org.glassfish.jersey.internal.Errors.process(Errors.java:297) > at org.glassfish.jersey.internal.Errors.process(Errors.java:267) > at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:340) > at org.glassfish.jersey.client.ClientRuntime$3.run(ClientRuntime.java:210) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > eclipse.buildId=11.1.0.AM1-v20170824-1835-B873 > java.version=1.8.0_141 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > {code} -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26700) Get A rating on https://observatory.mozilla.org for tools.jboss.org

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26700?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26700: ------------------------------- Sprint: devex #169 July 2019, devex #172 Sep 2019, devex #170 Aug 2019, devex #171 Aug 2019 (was: devex #169 July 2019, devex #170 Aug 2019, devex #171 Aug 2019) > Get A rating on https://observatory.mozilla.org for tools.jboss.org > ------------------------------------------------------------------- > > Key: JBIDE-26700 > URL: https://issues.jboss.org/browse/JBIDE-26700 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Affects Versions: 4.12.0.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.13.0.AM1 > > -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4735) Central projects Wizard sometimes fails to open

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBDS-4735?page=com.atlassian.jira.plugin.... ] Jeff MAURY updated JBDS-4735: ----------------------------- Sprint: devex #159 December 2018, devex #161 January 2019, devex #162 February 2019, devex #163 March 2019, devex #164 April 2019, devex #165 April 2019, devex #166 May 2019, devex #167 June 2019, devex #168 June 2019, devex #169 July 2019, devex #172 Sep 2019, devex #170 Aug 2019, devex #171 Aug 2019 (was: devex #159 December 2018, devex #161 January 2019, devex #162 February 2019, devex #163 March 2019, devex #164 April 2019, devex #165 April 2019, devex #166 May 2019, devex #167 June 2019, devex #168 June 2019, devex #169 July 2019, devex #170 Aug 2019, devex #171 Aug 2019) > Central projects Wizard sometimes fails to open > ----------------------------------------------- > > Key: JBDS-4735 > URL: https://issues.jboss.org/browse/JBDS-4735 > Project: Red Hat CodeReady Studio (devstudio) > Issue Type: Bug > Components: central > Affects Versions: 12.9.0.GA > Environment: manually Fedora 28, automation > Reporter: Vojtech Prusa > Assignee: Jeff MAURY > Priority: Major > Fix For: 12.13.0.AM1 > > Attachments: central.tar.gz, image-2018-10-17-09-24-31-555.png, screenshot-1.png > > > There is "openInIDE" used in 3 places in "main.min.js" in central source code*. When the central reloads and works normally, "openInIDE" is a function (probably defined in Java code or somewhere out of the "main.min.js" file) with following implementation: > function openInIDE() { > var result = callJava(1, '9aee3b4a3f3b40ed26f47d66375b25e3', Array.prototype.slice.call(arguments)); > if (typeof result == 'string' && result.indexOf('org.eclipse.swt.browser.error') == 0) { > var error = new Error(result.substring(29)); > throw error; > } > return result; > } > After the issue appears, "typedef openInIDE" is undefined, which causes probably the issues. > *Additional information to the 3 places, where "openInIDE" appears - it appears in 2 functions: > - registerButtonClicks() - here is the "openInIDE" needed for loading and displaying the central correctly > - delegateToIDE(a, b) - here is the "openInIDE" needed for opening the wizard to the quickstart > OLDER DESCRIPTION (does not describes the issue enough, but I decided to keep it for more details about the issue): > ---------------------------------------------------------------------------------------------------------------------- > Sometimes central examples wizards fail to load and modal dialog is shown instead (screen attached). > Nothing in Error log view. > Restarting devstudio solves the issue. > Adding screen and central tar of: > devstudio-12.9.0.GA-v20180928-1629-B3448/workspaces/workspace/.metadata/.plugins/org.jboss.tools.central/central > Addition info: > Considering that central itests fails for this sometimes fresh installation without restart may cause this. Although it happen again after running devstudio for some time and restarting Central view. -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26742) Create RedDeer methods for working with submodules of a module (module of a project deployed to server)

by Zbyněk Červinka (Jira)

[ https://issues.jboss.org/browse/JBIDE-26742?page=com.atlassian.jira.plugi... ] Zbyněk Červinka updated JBIDE-26742: ------------------------------------ Story Points: 8 > Create RedDeer methods for working with submodules of a module (module of a project deployed to server) > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26742 > URL: https://issues.jboss.org/browse/JBIDE-26742 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Affects Versions: 4.13.0.AM1 > Reporter: Zbyněk Červinka > Assignee: Zbyněk Červinka > Priority: Major > Fix For: 4.13.0.AM1 > > Attachments: The Servers view.png > > > Methods has to work using the "Servers" view in the Red Hat CodeReady Studio. -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26787) Several tests in examples.wildfly.itests are failing due to "Exception during sync execution in UI thread"

by Zbyněk Červinka (Jira)

[ https://issues.jboss.org/browse/JBIDE-26787?page=com.atlassian.jira.plugi... ] Zbyněk Červinka updated JBIDE-26787: ------------------------------------ Story Points: 3 > Several tests in examples.wildfly.itests are failing due to "Exception during sync execution in UI thread" > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26787 > URL: https://issues.jboss.org/browse/JBIDE-26787 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests, project-examples > Affects Versions: 4.13.0.AM1 > Environment: All, tests are failing sporadically. > Reporter: Zbyněk Červinka > Assignee: Zbyněk Červinka > Priority: Major > > Several tests in examples.wildfly.itests are failing due to "Exception during sync execution in UI thread" > h2. *Jenkins:* > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples... > h2. *Stack Trace:* > org.eclipse.reddeer.common.exception.RedDeerException: Exception during sync execution in UI thread > at org.jboss.tools.examples.ui.bot.test.integration.WildFlyImportQuickstartsTest.quickstartTest(WildFlyImportQuickstartsTest.java:62) > Caused by: org.eclipse.swt.SWTException: Widget is disposed > h2. *Standard Error:* > org.eclipse.reddeer.common.exception.RedDeerException: Exception during sync execution in UI thread > at org.eclipse.reddeer.common.util.Display.handleErrorOccured(Display.java:112) > at org.eclipse.reddeer.common.util.Display.syncExec(Display.java:84) > at org.eclipse.reddeer.core.handler.TreeItemHandler.getText(TreeItemHandler.java:68) > at org.eclipse.reddeer.swt.impl.tree.AbstractTreeItem.getCell(AbstractTreeItem.java:77) > at org.eclipse.reddeer.eclipse.ui.problems.Problem.getCell(Problem.java:68) > at org.eclipse.reddeer.eclipse.ui.markers.AbstractMarker.getDescription(AbstractMarker.java:43) > at org.jboss.tools.central.reddeer.api.ExamplesOperator.getAllWarnings(ExamplesOperator.java:225) > at org.jboss.tools.examples.ui.bot.test.integration.AbstractImportQuickstartsTest.checkForWarnings(AbstractImportQuickstartsTest.java:375) > at org.jboss.tools.examples.ui.bot.test.integration.AbstractImportQuickstartsTest.runQuickstarts(AbstractImportQuickstartsTest.java:283) > at org.jboss.tools.examples.ui.bot.test.integration.WildFlyImportQuickstartsTest.quickstartTest(WildFlyImportQuickstartsTest.java:62) > at jdk.internal.reflect.GeneratedMethodAccessor185.invoke(Unknown Source) > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:566) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > > ... -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26758) examples.wildfly.itests contains errors like "There is no project with name " for projects: dist, wicket-ear and helloworld-classfiletransformer

by Zbyněk Červinka (Jira)

[ https://issues.jboss.org/browse/JBIDE-26758?page=com.atlassian.jira.plugi... ] Zbyněk Červinka updated JBIDE-26758: ------------------------------------ Story Points: 3 > examples.wildfly.itests contains errors like "There is no project with name " for projects: dist, wicket-ear and helloworld-classfiletransformer > ------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-26758 > URL: https://issues.jboss.org/browse/JBIDE-26758 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.12.0.Final > Environment: OS X 10.14.5 > Reporter: Zbyněk Červinka > Assignee: Zbyněk Červinka > Priority: Major > > h2. examples.wildfly.itests contains errors like "There is no project with name " for projects: > * dist > * wicket-ear > * helloworld-classfiletransformer > h2. *Error messages:* > "There is no project with name jboss-dist" > "There is no project with name jboss-wicket-ear" > "There is no project with name jboss-helloworld-classfiletransformer" > h2. *Reason for this error* - project's folder name is different from the artifact id in the pom.xml -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 9 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 September 2019