August 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26275) CDK itests stabilization on multiple platforms

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26275?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-26275: ---------------------------------- Sprint: devex #153 August 2018 > CDK itests stabilization on multiple platforms > ---------------------------------------------- > > Key: JBIDE-26275 > URL: https://issues.jboss.org/browse/JBIDE-26275 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk, integration-tests > Affects Versions: 4.9.0.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Fix For: 4.9.0.AM2 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26275) CDK itests stabilization on multiple platforms

by Ondrej Dockal (JIRA)

Ondrej Dockal created JBIDE-26275: ------------------------------------- Summary: CDK itests stabilization on multiple platforms Key: JBIDE-26275 URL: https://issues.jboss.org/browse/JBIDE-26275 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: cdk, integration-tests Affects Versions: 4.9.0.AM1 Reporter: Ondrej Dockal Assignee: Ondrej Dockal Fix For: 4.9.0.AM2 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26063) POC Unit/Functional/Integration Tests for SSP

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26063?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-26063: ------------------------------- Sprint: devex #150 June 2018, devex #151 June 2018, devex #153 August 2018 (was: devex #150 June 2018, devex #151 June 2018, devex #152 July 2018) > POC Unit/Functional/Integration Tests for SSP > --------------------------------------------- > > Key: JBIDE-26063 > URL: https://issues.jboss.org/browse/JBIDE-26063 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests, runtime-server-protocol > Reporter: Pavol Srna > Assignee: Jan Richter > Fix For: 4.9.0.AM1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25207) Integration Tests: PortForwardingTest

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25207?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-25207: ---------------------------------- Sprint: devex #153 August 2018 (was: devex #152 July 2018) > Integration Tests: PortForwardingTest > ------------------------------------- > > Key: JBIDE-25207 > URL: https://issues.jboss.org/browse/JBIDE-25207 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM3 > Environment: Windows 10 > Reporter: Andre Dietisheim > Assignee: Josef Kopriva > Labels: integration_tests > Fix For: 4.9.x > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26179) New Application Wizard: Add refresh button for project selection/Better selection of projects

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26179?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-26179: ---------------------------------- Sprint: devex #153 August 2018 (was: devex #152 July 2018) > New Application Wizard: Add refresh button for project selection/Better selection of projects > --------------------------------------------------------------------------------------------- > > Key: JBIDE-26179 > URL: https://issues.jboss.org/browse/JBIDE-26179 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.6.0.Final > Environment: F28 > console.engint.openshift.com > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Fix For: 4.9.0.AM1 > > > In New Application Wizard could be added button for refresh of projects. The reason is, in some cases this is not refreshed. > Workflow: > 1. Create connection to console engint.openshift.com > 2. Delete all projects in connection > 3. Open New Application Wizard from File -> New > 4. Select connection > 5. When you are asked to create project create it > 6. Now you should be on New Application Wizard, but project is not selected > Workaround: You can click on Back and Next afterwards, so you can see now project. > I suppose this issue is caused with slower server response, so user should be able to to refresh projects list and maybe edit projects(if he enter wrong name...). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26098) Update dependencies in org.jboss.tools.stacks and repair test failures in jbosstools_base-master job

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26098?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-26098: ---------------------------------- Sprint: devex #151 June 2018, devex #153 August 2018 (was: devex #151 June 2018) > Update dependencies in org.jboss.tools.stacks and repair test failures in jbosstools_base-master job > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-26098 > URL: https://issues.jboss.org/browse/JBIDE-26098 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: qa > Affects Versions: 4.6.0.Final > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Fix For: 4.9.0.AM1 > > > 1. Have stacks tests to be run on jenkins jbt-base master and pull request job and have them green (not just omitting stacks tests results). > 2. Update versions of maven plugins used as libraries in org.jboss.tools.stacks plugin: > * org.jboss.jdf.stacks-client; 1.0.3.Final -> no change > * org.yaml.snakeyaml; 1.10 -> 1.18 > * org.apache.httpcomponents.httpclient; 4.0.1 -> 4.5.5 > * org.apache.httpcomponents.httpcore; 4.0.1 -> 4.4.9 > * org.jboss.logging.jboss-logging; 3.1.2.GA -> 3.3.2.Final > 3. Run all stacks.tests available (only one test class was run) > 4. Check on dependencies and usages in org.jboss.jdf.stacks-client and org.jboss.tools.stacks (what needs to be update, does it broke something, what else is using it) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26085) Rewrite CDK itests to use cdk downloaded via download runtime wizard

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26085?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-26085: ---------------------------------- Sprint: devex #153 August 2018 > Rewrite CDK itests to use cdk downloaded via download runtime wizard > -------------------------------------------------------------------- > > Key: JBIDE-26085 > URL: https://issues.jboss.org/browse/JBIDE-26085 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk, integration-tests > Affects Versions: 4.6.0.AM2 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Fix For: 4.9.x > > > Implement DownloadCDKRuntime requirement that will get CDK and configure it via setup-cdk. Requirement should be use once to download latest cdk bits and reuse it for all suitable test classes. > Next step it to avoid using cdk-scripts as much as possible as so simplify setting up cdk in jenkins jobs. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26144) Update jboss-stacks minishift.yaml with newer released versions of CDK and minishift

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26144?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-26144: ---------------------------------- Sprint: devex #153 August 2018 > Update jboss-stacks minishift.yaml with newer released versions of CDK and minishift > ------------------------------------------------------------------------------------ > > Key: JBIDE-26144 > URL: https://issues.jboss.org/browse/JBIDE-26144 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: cdk, qa > Affects Versions: 4.6.0.Final > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Fix For: 4.9.0.AM1 > > > * Add missing released minishift runtimes (1.18, 1.19, 1.20, 1.21) > * Insert CDK 3.5.0 when it is released > * improve unit tests for stack file validation (add complex http request check) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4722) Problem creating splash implementation

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBDS-4722?page=com.atlassian.jira.plugin.... ] Ondrej Dockal commented on JBDS-4722: ------------------------------------- Sure, just scroll down the stack trace, there is Session data section, which probably answers all your questions. It was fedora 28 and devstudio 12.9.0.AM1 staging bits available in https://devstudio.redhat.com/12/staging/builds/, java 1.8.0_172. > Problem creating splash implementation > -------------------------------------- > > Key: JBDS-4722 > URL: https://issues.jboss.org/browse/JBDS-4722 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: product > Affects Versions: 12.9.0.AM1 > Reporter: Ondrej Dockal > > I got a bunch of error while restarting/starting over devstudio. > {code} > Problem creating splash implementation > java.lang.UnsupportedClassVersionError: com/jboss/devstudio/core/splash/SplashHandler has been compiled by a more recent version of the Java Runtime (class file version 53.0), this version of the Java Runtime only recognizes class file versions up to 52.0 > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:763) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.defineClass(ModuleClassLoader.java:276) > at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.defineClass(ClasspathManager.java:632) > at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findClassImpl(ClasspathManager.java:555) > at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClassImpl(ClasspathManager.java:514) > at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:501) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:328) > at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:392) > at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:470) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:419) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:411) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:150) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at org.eclipse.osgi.internal.framework.EquinoxBundle.loadClass(EquinoxBundle.java:609) > at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:177) > at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:931) > at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243) > at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:60) > at org.eclipse.ui.internal.WorkbenchPlugin.lambda$0(WorkbenchPlugin.java:288) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:71) > at org.eclipse.ui.internal.WorkbenchPlugin.createExtension(WorkbenchPlugin.java:285) > at org.eclipse.ui.internal.splash.SplashHandlerFactory$1.run(SplashHandlerFactory.java:134) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.splash.SplashHandlerFactory.create(SplashHandlerFactory.java:129) > at org.eclipse.ui.internal.splash.SplashHandlerFactory.processElement(SplashHandlerFactory.java:112) > at org.eclipse.ui.internal.splash.SplashHandlerFactory.findSplashHandlerFor(SplashHandlerFactory.java:60) > at org.eclipse.ui.internal.Workbench.getSplash(Workbench.java:892) > at org.eclipse.ui.internal.Workbench.access$2(Workbench.java:884) > at org.eclipse.ui.internal.Workbench$2.run(Workbench.java:782) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.Workbench.createSplashWrapper(Workbench.java:846) > at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:597) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:560) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:152) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:656) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:592) > at org.eclipse.equinox.launcher.Main.run(Main.java:1498) > at org.eclipse.equinox.launcher.Main.main(Main.java:1471) > Session data: > eclipse.buildId=12.9.0.AM1-v20180726-1026-B3091 > java.version=1.8.0_172 > 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.5.0#75005)

7 years, 8 months

1
0
0 / 0

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

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26160?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-26160: ------------------------------------- Sprint: devex #153 August 2018 (was: devex #152 July 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 > Labels: server_adapter > Fix For: 4.9.0.AM2 > > > 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. The new pod is not running in debug (dev-) mode any more. To have it running again you need to restart the server adapter into debug, which will re-create a new pod in debug-mode. > 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.5.0#75005)

7 years, 8 months

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 August 2018