August 2018 - jbosstools-issues - Jboss List Archives

[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 reassigned JBDS-4722: ----------------------------------- Assignee: Nick Boldt (was: Ondrej Dockal) > 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 > Assignee: Nick Boldt > Fix For: 12.9.0.AM3 > > > 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)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23732) Implement new batch integration ui tests for content assist features in job.xml file.

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23732?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-23732: ---------------------------------- Fix Version/s: 4.9.0.AM3 (was: 4.9.x) > Implement new batch integration ui tests for content assist features in job.xml file. > -------------------------------------------------------------------------------------- > > Key: JBIDE-23732 > URL: https://issues.jboss.org/browse/JBIDE-23732 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: integration-tests, qa > Affects Versions: 4.4.2.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Labels: batch, integration_tests > Fix For: 4.9.0.AM3 > > > These tests covers both view tabs where content assist feature is used (design and source view). Test: > 1. Offered batch artifacts in content assist menu for ref attribute > 2. Offered element's id for id attribute with correct level of context > 3. Fully qualified names of exceptions used in class attribute of include/exclude tag > 4. Properties from both property definition in job.xml and from batch artifact with @BatchProperty annotation > 5. Proper list of element's id referred from next, to attributes and/or restart attributes -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23732) Implement new batch integration ui tests for content assist features in job.xml file.

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23732?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-23732: ---------------------------------- Sprint: devex #154 September 2018 > Implement new batch integration ui tests for content assist features in job.xml file. > -------------------------------------------------------------------------------------- > > Key: JBIDE-23732 > URL: https://issues.jboss.org/browse/JBIDE-23732 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: integration-tests, qa > Affects Versions: 4.4.2.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Labels: batch, integration_tests > Fix For: 4.9.0.AM3 > > > These tests covers both view tabs where content assist feature is used (design and source view). Test: > 1. Offered batch artifacts in content assist menu for ref attribute > 2. Offered element's id for id attribute with correct level of context > 3. Fully qualified names of exceptions used in class attribute of include/exclude tag > 4. Properties from both property definition in job.xml and from batch artifact with @BatchProperty annotation > 5. Proper list of element's id referred from next, to attributes and/or restart attributes -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

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: ---------------------------------- Fix Version/s: (was: 4.9.x) > 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.0.AM3 > > > 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)

6 years, 1 month

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 #154 September 2018 (was: devex #151 June 2018, devex #153 August 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.AM3 > > > 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)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26281) get*LaunchAttributes methods return null

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26281?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-26281. ------------------------------- !https://media.giphy.com/media/BIuuwHRNKs15C/giphy.gif! > get*LaunchAttributes methods return null > ---------------------------------------- > > Key: JBIDE-26281 > URL: https://issues.jboss.org/browse/JBIDE-26281 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-server-protocol > Reporter: Jan Richter > Assignee: Rob Stryker > Fix For: 4.9.0.AM1 > > > Created a WildFly 13 server adapter and got a server handle back. > Now when I call the following, I get null back (handle is a valid server handle in this case). > {noformat}server/getRequiredLaunchAttributes({id: handle.id, mode: 'run'}){noformat} > The same goes for server/getOptionalLaunchAttributes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26284) Servers created from relative path can't start

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26284?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-26284. ------------------------------- Works for me. > Servers created from relative path can't start > ---------------------------------------------- > > Key: JBIDE-26284 > URL: https://issues.jboss.org/browse/JBIDE-26284 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-server-protocol > Reporter: Jan Richter > Assignee: Rob Stryker > Fix For: 4.9.0.AM1 > > > Servers created with their ''server.home.dir'' attribute set to a relative path will error on starting. > Example log from wildfly (and yes, that is the complete log): > {noformat}Error: Could not find or load main class org.jboss.modules.Main{noformat} > Relative paths either need to be resolved, or rejected. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26285) stopServerAsync returns ok when stopping a stopped server

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26285?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-26285. ------------------------------- Verified, closing. > stopServerAsync returns ok when stopping a stopped server > --------------------------------------------------------- > > Key: JBIDE-26285 > URL: https://issues.jboss.org/browse/JBIDE-26285 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-server-protocol > Reporter: Jan Richter > Assignee: Rob Stryker > Fix For: 4.9.0.AM1 > > > Calling server/stopServerAsync on a server that is already stopped returns: > {noformat}{ severity: 0, pluginId: 'unknown', code: 0, message: 'ok' }{noformat} > There is no indication that the server wasn't actually stopped as a result of the request. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-25433) Investigate OSOOS for use for OpenShift ITests

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25433?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-25433. --------------------------------- Resolution: Won't Do The support for OSOOS will be dropped in the next couple of months, so this task is outdated. > Investigate OSOOS for use for OpenShift ITests > ---------------------------------------------- > > Key: JBIDE-25433 > URL: https://issues.jboss.org/browse/JBIDE-25433 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, openshift > Affects Versions: 4.5.2.AM2 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Fix For: 4.9.0.AM3 > > > https://docs.engineering.redhat.com/display/CentralCI/OpenShift+on+OpenStack -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-25433) Investigate OSOOS for use for OpenShift ITests

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25433?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-25433: ---------------------------------- Fix Version/s: 4.9.0.AM3 (was: 4.9.x) > Investigate OSOOS for use for OpenShift ITests > ---------------------------------------------- > > Key: JBIDE-25433 > URL: https://issues.jboss.org/browse/JBIDE-25433 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, openshift > Affects Versions: 4.5.2.AM2 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Fix For: 4.9.0.AM3 > > > https://docs.engineering.redhat.com/display/CentralCI/OpenShift+on+OpenStack -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

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 2018