December 2018 - jbosstools-issues

[JBoss JIRA] (JBIDE-26408) Server adapter: debugging fails for nodejs-mongo-persistent template based application

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26408?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26408: ------------------------------- Sprint: devex #156 October 2018, devex #157 November 2019, devex #158 November 2018 (was: devex #156 October 2018, devex #157 November 2019, devex #158 November 2018, devex #159 December 2018) > Server adapter: debugging fails for nodejs-mongo-persistent template based application > -------------------------------------------------------------------------------------- > > Key: JBIDE-26408 > URL: https://issues.jboss.org/browse/JBIDE-26408 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.9.0.Final > Environment: cdk-3.6.0 > Reporter: Andre Dietisheim > Assignee: Jeff MAURY > Priority: Major > Labels: node, server_adapter > Fix For: 4.11.x > > Attachments: change-nodejs-version.png, screenshot-1.png, screenshot-2.png > > > steps: > # ASSERT: have cdk 3.6.0 > # EXEC: create an application based on the *nodejs-mongo-persistent* template, have the application imported to the workspace and the server adapter created for it > # EXEC: start the server adapter > # ASSERT: server adapter is *[Started, Synchronized]* > # EXEC: Restart the adapter into debugging > Result: > You very quickly (the timeout seems very short) get an error dialog telling you that the debugger could not connect. > !screenshot-1.png! > The debugger is therefore stopped, debugging wont work. > !screenshot-2.png! > Trying to restart it reproduces the error that we already have. > In the Eclipse log you'll find the following: > {code} > java.io.IOException: Timed out waiting for handshake > at org.eclipse.wst.jsdt.chromium.internal.v8native.JavascriptVmImpl.newIOException(JavascriptVmImpl.java:114) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:134) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attach(StandaloneVmImpl.java:79) > at org.eclipse.wst.jsdt.chromium.debug.core.model.JavascriptVmEmbedderFactory$4$1.attach(JavascriptVmEmbedderFactory.java:207) > at org.eclipse.wst.jsdt.chromium.debug.core.model.DebugTargetImpl.attach(DebugTargetImpl.java:74) > at org.eclipse.wst.jsdt.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:101) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:859) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:717) > at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1026) > at org.eclipse.debug.internal.ui.DebugUIPlugin$2.run(DebugUIPlugin.java:1240) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60) > Caused by: java.util.concurrent.TimeoutException > at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:204) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:127) > ... 9 more > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4743) When saving an xhtml file, getting JSF error popup

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBDS-4743?page=com.atlassian.jira.plugin.... ] Jeff MAURY updated JBDS-4743: ----------------------------- Sprint: devex #158 November 2018 (was: devex #158 November 2018, devex #159 December 2018) > When saving an xhtml file, getting JSF error popup > -------------------------------------------------- > > Key: JBDS-4743 > URL: https://issues.jboss.org/browse/JBDS-4743 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: jsf > Affects Versions: 12.9.0.GA > Environment: JBDS 12.9 on macOS mojave > Reporter: Fabi Yo > Assignee: Jeff MAURY > Priority: Major > Fix For: 12.x > > Attachments: Schermafbeelding 2018-11-07 om 9.42.32 AM.png, fieldWizard.xhtml, log.txt, web.xml > > > I am working on an xhtml file which contains JSF tags. I can work normally in it. After a while (random) when I save an xhtml file, I get this popup saying: > 'Refreshing JSF information about: ..... ' > An internal error occured. > The problem is, from the moment i get it, it doesn't stop. After a while it gets very annoying. > I wish I could tell you more, but the error popup is quite vague... > See more info in the picture in attachment -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4748) PR to change name of Fabric8 analytics Devstudio plugin

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBDS-4748?page=com.atlassian.jira.plugin.... ] Jeff MAURY reassigned JBDS-4748: -------------------------------- Assignee: Jeff MAURY > PR to change name of Fabric8 analytics Devstudio plugin > ------------------------------------------------------- > > Key: JBDS-4748 > URL: https://issues.jboss.org/browse/JBDS-4748 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: central-update > Reporter: Geetika Batra > Assignee: Jeff MAURY > Priority: Minor > > The following PR's change the name of fabric8 analytics Devstudio Plugin to Dependency Analytics. > https://github.com/jbosstools/jbosstools-discovery/compare/master...Geeti... > https://github.com/jbosstools/jbosstools-discovery/compare/master...Geeti... -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4748) PR to change name of Fabric8 analytics Devstudio plugin

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBDS-4748?page=com.atlassian.jira.plugin.... ] Jeff MAURY updated JBDS-4748: ----------------------------- Sprint: devex #159 December 2018 > PR to change name of Fabric8 analytics Devstudio plugin > ------------------------------------------------------- > > Key: JBDS-4748 > URL: https://issues.jboss.org/browse/JBDS-4748 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: central-update > Reporter: Geetika Batra > Assignee: Jeff MAURY > Priority: Minor > > The following PR's change the name of fabric8 analytics Devstudio Plugin to Dependency Analytics. > https://github.com/jbosstools/jbosstools-discovery/compare/master...Geeti... > https://github.com/jbosstools/jbosstools-discovery/compare/master...Geeti... -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 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 > Central projects Wizard sometimes fails to open > ----------------------------------------------- > > Key: JBDS-4735 > URL: https://issues.jboss.org/browse/JBDS-4735 > Project: Red Hat JBoss Developer 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.x > > Attachments: central.tar.gz, image-2018-10-17-09-24-31-555.png, screenshot-1.png > > > 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 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26459) Opening RH Central shows multiple errors with Java 11

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26459?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26459: ------------------------------- Sprint: devex #159 December 2018 > Opening RH Central shows multiple errors with Java 11 > ----------------------------------------------------- > > Key: JBIDE-26459 > URL: https://issues.jboss.org/browse/JBIDE-26459 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.10.0.AM1 > Environment: Fedora 28, Java 11 (Oracle jdk-11.0.1) > Reporter: Ondrej Dockal > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.11.x > > Attachments: Screenshot_20181029_171518.png > > > I got Oracle's open jdk 11.0.1 version and installed devstudio with it, when devstudio is run, red hat central page is open by default, this brings multiple errors, as Java 11 is dropping some java ee modules (https://openjdk.java.net/jeps/320). > Issue description: > {code} > eclipse.buildId=12.10.0.AM1-v20181026-0745-B3616 > java.version=11.0.1 > 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 > org.eclipse.core.jobs > Error > Mon Oct 29 16:47:19 CET 2018 > An internal error occurred during: "Update project wizard list". > java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException > at org.jboss.tools.project.examples.internal.FavoriteExampleManager.<init>(FavoriteExampleManager.java:38) > at org.jboss.tools.project.examples.internal.FavoriteExampleManager.<init>(FavoriteExampleManager.java:31) > at org.jboss.tools.project.examples.internal.ProjectExamplesActivator.getFavoriteExampleManager(ProjectExamplesActivator.java:1067) > at org.jboss.tools.central.editors.GettingStartedHtmlPage$5$2.collectFavorites(GettingStartedHtmlPage.java:283) > at org.jboss.tools.central.editors.GettingStartedHtmlPage$5$2.run(GettingStartedHtmlPage.java:274) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63) > Caused by: java.lang.ClassNotFoundException: javax.xml.bind.JAXBException cannot be found by org.jboss.tools.project.examples_3.1.201.v20180802-1534 > at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:511) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:422) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:414) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:153) > at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) > ... 6 more > {code} > and > {code} > eclipse.buildId=12.10.0.AM1-v20181026-0745-B3616 > java.version=11.0.1 > 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 > org.eclipse.core.jobs > Error > Mon Oct 29 16:47:20 CET 2018 > An internal error occurred during: "Download quickstarts list". > java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException > at org.jboss.tools.project.examples.model.ProjectExampleUtil.fetchCategories(ProjectExampleUtil.java:396) > at org.jboss.tools.project.examples.model.ProjectExampleUtil.getCategories(ProjectExampleUtil.java:273) > at org.jboss.tools.project.examples.model.ProjectExampleUtil.getCategories(ProjectExampleUtil.java:263) > at org.jboss.tools.project.examples.internal.ProjectExampleXmlProvider.getExamples(ProjectExampleXmlProvider.java:28) > at org.jboss.tools.project.examples.internal.ProjectExampleManager.getExamples(ProjectExampleManager.java:60) > at org.jboss.tools.central.editors.GettingStartedHtmlPage$RefreshQuickstartsJob.run(GettingStartedHtmlPage.java:102) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63) > Caused by: java.lang.ClassNotFoundException: javax.xml.bind.JAXBException cannot be found by org.jboss.tools.project.examples_3.1.201.v20180802-1534 > at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:511) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:422) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:414) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:153) > at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) > ... 7 more > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24442) Import wizard: does nothing if server is not reachable

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-24442?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24442: ------------------------------- Sprint: devex #156 October 2018, devex #157 November 2019, devex #158 November 2018 (was: devex #156 October 2018, devex #157 November 2019, devex #158 November 2018, devex #159 December 2018) > Import wizard: does nothing if server is not reachable > ------------------------------------------------------ > > Key: JBIDE-24442 > URL: https://issues.jboss.org/browse/JBIDE-24442 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.Final > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Priority: Major > Fix For: 4.11.x > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24646) Import application: doesnt check if local branch match

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-24646?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24646: ------------------------------- Sprint: devex #156 October 2018, devex #157 November 2019, devex #158 November 2018 (was: devex #156 October 2018, devex #157 November 2019, devex #158 November 2018, devex #159 December 2018) > Import application: doesnt check if local branch match > ------------------------------------------------------ > > Key: JBIDE-24646 > URL: https://issues.jboss.org/browse/JBIDE-24646 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.0.AM1 > Reporter: Jan Novak > Assignee: Dmitrii Bocharov > Priority: Major > Labels: import_app, openshift_v3 > Fix For: 4.11.x > > > Importing project from Openshift > * use existing repo > * local repo uses different branch than Openshift > * remote branch isnt locally fetched > * import finishes succesfully > * in local repo is *stil checkouted wrong branch*, without any warnings -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26330) Server adapter: shutting down Eclipse won't reset the maven profile that the adapter activated in the project

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26330?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26330: ------------------------------- Sprint: devex #156 October 2018, devex #157 November 2019, devex #158 November 2018 (was: devex #156 October 2018, devex #157 November 2019, devex #158 November 2018, devex #159 December 2018) > Server adapter: shutting down Eclipse won't reset the maven profile that the adapter activated in the project > ------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26330 > URL: https://issues.jboss.org/browse/JBIDE-26330 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.9.0.AM2 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Priority: Major > Fix For: 4.11.x > > > steps: > # EXEC: create the "hello" application in OpenShift as outlined in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello... > # EXEC: import the "hello" maven project into your Eclipse > # EXEC: create a server adapter and start it > # ASSERT: server adapter for project "hello" is *[Started, Synchronized]* > # EXEC: in the Project Explorer: pick Maven > Select Maven Profiles... > # ASSERT: *"openshift"* maven profile is selected > # EXEC: Restart Eclipse > # ASSERT: server adapter for project "hello" is *[Stopped, Republish]* > # EXEC: in the Project Explorer: pick Maven > Select Maven Profiles... > Result: > Project "hello" still has *"openshift"* profile selected > Expected result: > Project "hello" still has *no profile* selected (starting the server adapter selects the "openshift" profile, while stopping it unselects it.) -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26160) Server Adapter: erroneously stays in [Debugging] when you kill the pod

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26160?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26160: ------------------------------- Sprint: devex #154 September 2018, devex #155 September 2018, devex #156 October 2018, devex #157 November 2019, devex #158 November 2018 (was: devex #154 September 2018, devex #155 September 2018, devex #156 October 2018, devex #157 November 2019, devex #158 November 2018, devex #159 December 2018) > Server Adapter: erroneously stays in [Debugging] when you kill the pod > ---------------------------------------------------------------------- > > Key: JBIDE-26160 > URL: https://issues.jboss.org/browse/JBIDE-26160 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.6.0.AM3 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Priority: Major > Labels: server_adapter > Fix For: 4.11.x > > > steps: > # EXEC: create an application (via ex. nodejs-mongo-persistent template), import the project and create a server adapter for it > # ASSERT: server adapter is created > # EXEC: start the server adapter in Debugging > # ASSERT: sever adapter is in *[Debugging, Synchronized]* state > # ASSERT: select pod and pick "Port Forwarding..." and it states that the forwarding is started > # EXEC: in Explorer: select the pod for your service and pick "Delete" > # ASSERT: pod gets deleted and recreated > # ASSERT: select pod and pick "Port Forwarding..." and it states that the forwarding is stopped > Result: > The server adapter still says that is is *[Debugging, Synchronized]*, but debugging is not working any more. Debugging doesn't work any more because the port forwarding was stopped. To have it running again you need to restart the port forwarding for the new pod. > Expected result: > Server adapter should get out of debugging and back into normal run mode *[Started, Synchronized]*. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 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 December 2018