April 2019 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4712) Installing JBDS onto Eclipse photon (aka BYOE) shows certificate selection dialog

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBDS-4712?page=com.atlassian.jira.plugin.... ] Ondrej Dockal updated JBDS-4712: -------------------------------- Fix Version/s: 12.11.0.GA (was: 12.10.0.AM1) > Installing JBDS onto Eclipse photon (aka BYOE) shows certificate selection dialog > --------------------------------------------------------------------------------- > > Key: JBDS-4712 > URL: https://issues.jboss.org/browse/JBDS-4712 > Project: Red Hat CodeReady Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 12.0.0.AM3, 12.0.0.GA > Environment: Eclipse Photon, > RHEL7 (automation), fedora27 (local), most likely not OS related. > Reporter: Vojtech Prusa > Assignee: Ondrej Dockal > Priority: Major > Fix For: 12.11.0.GA > > > Hello, > I am fixing and updating devstudio installer tests and i have run into issue about which i am not sure if its is relevant. > Automation of installer tests fails on Installing JBDS onto Eclipse with following message: > "java.lang.AssertionError: Selection Needed window has been displayed." > Full message is here: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > If ifgnored installation ends up successfully. > Error line: > https://github.com/vprusa/jbdevstudio-qa/blame/master/devstudio-installer... > Tests were executed against my git fork with fixes not merged yet, the original line is here: > https://github.com/jbdevstudio/jbdevstudio-qa/blame/master/devstudio-inst... > My question is: > Should i consider this as an error or not. > If yes then issue is filed, if no I will remove this line from the test. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4712) Installing JBDS onto Eclipse photon (aka BYOE) shows certificate selection dialog

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBDS-4712?page=com.atlassian.jira.plugin.... ] Ondrej Dockal commented on JBDS-4712: ------------------------------------- Issues solved as part of https://github.com/jbdevstudio/jbdevstudio-qa/pull/158/commits/588e69a2a7.... > Installing JBDS onto Eclipse photon (aka BYOE) shows certificate selection dialog > --------------------------------------------------------------------------------- > > Key: JBDS-4712 > URL: https://issues.jboss.org/browse/JBDS-4712 > Project: Red Hat CodeReady Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 12.0.0.AM3, 12.0.0.GA > Environment: Eclipse Photon, > RHEL7 (automation), fedora27 (local), most likely not OS related. > Reporter: Vojtech Prusa > Assignee: Ondrej Dockal > Priority: Major > Fix For: 12.x > > > Hello, > I am fixing and updating devstudio installer tests and i have run into issue about which i am not sure if its is relevant. > Automation of installer tests fails on Installing JBDS onto Eclipse with following message: > "java.lang.AssertionError: Selection Needed window has been displayed." > Full message is here: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > If ifgnored installation ends up successfully. > Error line: > https://github.com/vprusa/jbdevstudio-qa/blame/master/devstudio-installer... > Tests were executed against my git fork with fixes not merged yet, the original line is here: > https://github.com/jbdevstudio/jbdevstudio-qa/blame/master/devstudio-inst... > My question is: > Should i consider this as an error or not. > If yes then issue is filed, if no I will remove this line from the test. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26604) Cannot connect to JMX server connection with EAP 7.1 remote local system on Java 8

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26604?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26604: ------------------------------- Story Points: 8 > Cannot connect to JMX server connection with EAP 7.1 remote local system on Java 8 > ---------------------------------------------------------------------------------- > > Key: JBIDE-26604 > URL: https://issues.jboss.org/browse/JBIDE-26604 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx, server > Affects Versions: 4.11.0.Final > Environment: Fedora 29, openjdk 1.8.0-201 > Reporter: Ondrej Dockal > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.12.0.AM1 > > > {code} > eclipse.buildId=12.11.0.GA-v20190329-0120-B4247 > java.version=1.8.0_201 > 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: -data file:/home/odockal/workspace-12110GA-Respin-Java8-JMX/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > org.jboss.ide.eclipse.as.core > Error > Fri Mar 29 16:42:53 CET 2019 > Error connecting to remote JMX. Please ensure your server is properly configured for JMX access. > org.jboss.tools.jmx.core.JMXException: Error connecting to remote JMX. Please ensure your server is properly configured for JMX access. > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:228) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:161) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:136) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:131) > at org.jboss.tools.jmx.core.tree.NodeUtils.createObjectNameTree(NodeUtils.java:54) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.loadRoot(JBossServerConnection.java:113) > at org.jboss.tools.jmx.ui.internal.views.navigator.MBeanExplorerContentProvider$1.run(MBeanExplorerContentProvider.java:211) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63) > Caused by: java.io.EOFException: Read past end of file > at org.jboss.marshalling.SimpleDataInput.eofOnRead(SimpleDataInput.java:151) > at org.jboss.marshalling.SimpleDataInput.readUnsignedByteDirect(SimpleDataInput.java:294) > at org.jboss.marshalling.SimpleDataInput.readUnsignedByte(SimpleDataInput.java:249) > at org.jboss.marshalling.river.RiverUnmarshaller.start(RiverUnmarshaller.java:1346) > at org.jboss.remotingjmx.protocol.v2.Common.prepareForUnMarshalling(Common.java:140) > at org.jboss.remotingjmx.protocol.v2.Common.prepareForUnMarshalling(Common.java:110) > at org.jboss.remotingjmx.protocol.v2.ClientCommon$BaseResponseHandler.handle(ClientCommon.java:184) > at org.jboss.remotingjmx.protocol.v2.ClientCommon$MessageReceiver$1.run(ClientCommon.java:123) > 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) > {code} > console log: > {code} > 16:42:53,240 WARN [org.jboss.remotingjmx.protocol.v2.ServerCommon] (pool-2-thread-1) Unexpected internal error: java.lang.ExceptionInInitializerError > at org.jboss.marshalling.river//org.jboss.marshalling.river.ClassDescriptors.<clinit>(ClassDescriptors.java:99) > at org.jboss.marshalling.river//org.jboss.marshalling.river.RiverUnmarshaller.doReadClassDescriptor(RiverUnmarshaller.java:1241) > at org.jboss.marshalling.river//org.jboss.marshalling.river.RiverUnmarshaller.doReadClassDescriptor(RiverUnmarshaller.java:1040) > at org.jboss.marshalling.river//org.jboss.marshalling.river.RiverUnmarshaller.doReadNewObject(RiverUnmarshaller.java:1354) > at org.jboss.marshalling.river//org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:275) > at org.jboss.marshalling.river//org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:208) > at org.jboss.marshalling//org.jboss.marshalling.AbstractObjectInput.readObject(AbstractObjectInput.java:76) > at org.jboss.remoting-jmx//org.jboss.remotingjmx.protocol.v2.ServerProxy$QueryNamesHandler.handle(ServerProxy.java:1102) > at org.jboss.remoting-jmx//org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1$1.run(ServerCommon.java:153) > at org.jboss.as.jmx//org.jboss.as.jmx.ServerInterceptorFactory$Interceptor$1.run(ServerInterceptorFactory.java:71) > at org.jboss.as.jmx//org.jboss.as.jmx.ServerInterceptorFactory$Interceptor$1.run(ServerInterceptorFactory.java:66) > at org.wildfly.security.elytron-private//org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:287) > at org.wildfly.security.elytron-private//org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:244) > at org.jboss.as.controller//org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254) > at org.jboss.as.controller//org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225) > at org.jboss.as.jmx//org.jboss.as.jmx.ServerInterceptorFactory$Interceptor.handleEvent(ServerInterceptorFactory.java:66) > at org.jboss.remoting-jmx//org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1.run(ServerCommon.java:149) > at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > at java.base/java.lang.Thread.run(Thread.java:834) > Caused by: java.lang.IllegalStateException: No standard field found for reverse order comparator! > at org.jboss.marshalling.river//org.jboss.marshalling.river.Protocol.<clinit>(Protocol.java:287) > ... 20 more > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26529) Large Project Explorer tree causes editor input to lag

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26529?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26529: ------------------------------- Sprint: devex #164 April 2019 (was: devex #164 April 2019, devex #165 April 2019) > Large Project Explorer tree causes editor input to lag > ------------------------------------------------------ > > Key: JBIDE-26529 > URL: https://issues.jboss.org/browse/JBIDE-26529 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jst > Affects Versions: 4.9.0.Final > Environment: Java 11, Eclipse 2019.03 JEE, Windows 7 > Reporter: Jesper Skov > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.12.0.AM1 > > Attachments: eclipse-bug-jboss.zip > > > We use JBoss Tools with Eclipse JEE distribution. > When Projetc Explorer contains a large tree (small elevator), performance of the java editor gets really bad with frequent lags. > I have first reported it as a problem against native Eclipse (https://bugs.eclipse.org/bugs/show_bug.cgi?id=543678) but it turns out the problem can only be reproduced when the feature 'org.jboss.tools.jst.feature.feature.group' is installed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26625) Fix builds for TP based on 2019-06M1

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26625?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26625: ------------------------------- Story Points: 5 > Fix builds for TP based on 2019-06M1 > ------------------------------------ > > Key: JBIDE-26625 > URL: https://issues.jboss.org/browse/JBIDE-26625 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.12.0.AM1 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.12.0.AM1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26622) Update 4.12.0.AM1 Target Platform (Docker tooling, ...)

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26622?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26622: ------------------------------- Story Points: 8 > Update 4.12.0.AM1 Target Platform (Docker tooling, ...) > ------------------------------------------------------- > > Key: JBIDE-26622 > URL: https://issues.jboss.org/browse/JBIDE-26622 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.12.0.AM1 > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.12.0.AM1 > > Attachments: p2diff_log_jbosstools_2019-04-04_16-45.txt, p2diff_log_jbosstools_2019-04-09_02-17.txt > > > Jira for tracking TP updates: > [~jeffmaury] Can you please update docker tooling on TP? The latest version includes fixes for running ITests with JDK1.8: https://git.eclipse.org/r/#/c/139834/ > Thank you! -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26603) NPE at org.jboss.tools.common.jdt.debug.internal.VmModelCache.getModel(VmModelCache.java:46)

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26603?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26603: ------------------------------- Story Points: 5 > NPE at org.jboss.tools.common.jdt.debug.internal.VmModelCache.getModel(VmModelCache.java:46) > -------------------------------------------------------------------------------------------- > > Key: JBIDE-26603 > URL: https://issues.jboss.org/browse/JBIDE-26603 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.11.0.Final > Environment: Fedora 29, Java 11 > Reporter: Ondrej Dockal > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.12.0.AM1 > > > {code} > !ENTRY org.eclipse.ui.navigator 4 2 2019-03-29 15:07:56.266 > !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.ui.navigator". > !STACK 0 > java.lang.NullPointerException > at org.jboss.tools.common.jdt.debug.internal.VmModelCache.getModel(VmModelCache.java:46) > at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getCachedVmModel(RemoteDebugActivator.java:143) > at org.jboss.tools.jmx.local.internal.JvmConnectionWrapper.getVmModel(JvmConnectionWrapper.java:244) > at org.jboss.tools.jmx.local.internal.JvmConnectionWrapper.debugEnabled(JvmConnectionWrapper.java:260) > at org.jboss.tools.jmx.ui.internal.views.navigator.ActionProvider.fillContextMenu(ActionProvider.java:119) > at org.eclipse.ui.navigator.NavigatorActionService$2.run(NavigatorActionService.java:228) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45) > at org.eclipse.ui.navigator.NavigatorActionService.addCommonActionProviderMenu(NavigatorActionService.java:222) > at org.eclipse.ui.navigator.NavigatorActionService.fillContextMenu(NavigatorActionService.java:177) > at org.eclipse.ui.navigator.CommonNavigatorManager.fillContextMenu(CommonNavigatorManager.java:258) > at org.eclipse.ui.navigator.CommonNavigatorManager.lambda$1(CommonNavigatorManager.java:270) > at org.eclipse.jface.action.MenuManager.fireAboutToShow(MenuManager.java:342) > at org.eclipse.jface.action.MenuManager.handleAboutToShow(MenuManager.java:473) > at org.eclipse.jface.action.MenuManager.access$1(MenuManager.java:468) > at org.eclipse.jface.action.MenuManager$2.menuShown(MenuManager.java:500) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:259) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:89) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5783) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1411) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1437) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1420) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1196) > at org.eclipse.reddeer.core.handler.MenuHandler.sendShowUI(MenuHandler.java:119) > at org.eclipse.reddeer.core.handler.MenuHandler$1.run(MenuHandler.java:59) > at org.eclipse.reddeer.core.handler.MenuHandler$1.run(MenuHandler.java:1) > at org.eclipse.reddeer.common.util.Display$ErrorHandlingRunnable.run(Display.java:162) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:40) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:185) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:5026) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4582) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1173) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1062) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:155) > at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:644) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:566) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:155) > at org.eclipse.reddeer.jdt.junit.UITestApplication.start(UITestApplication.java:69) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:137) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:107) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:566) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:661) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:597) > at org.eclipse.equinox.launcher.Main.run(Main.java:1476) > at org.eclipse.equinox.launcher.Main.main(Main.java:1449) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26506) Remediation page showing up when installing RHAMT from central - missing org.eclipse.emf.transaction

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26506?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26506: ------------------------------- Sprint: devex #161 January 2019, devex #162 February 2019, devex #163 March 2019, devex #164 April 2019 (was: devex #161 January 2019, devex #162 February 2019, devex #163 March 2019, devex #164 April 2019, devex #165 April 2019) > Remediation page showing up when installing RHAMT from central - missing org.eclipse.emf.transaction > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-26506 > URL: https://issues.jboss.org/browse/JBIDE-26506 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, central-update > Affects Versions: 4.11.0.AM1 > Reporter: Ondrej Dockal > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.12.0.AM1 > > > {code} > Cannot complete the install because one or more required items could not be found. > Software being installed: RHAMT 4.2.0.Final (org.jboss.tools.windup.feature.feature.group 4.2.0.Final) > Missing requirement: Model 4.2.0.Final (org.jboss.tools.windup.model 4.2.0.Final) requires 'osgi.bundle; org.eclipse.emf.transaction 0.0.0' but it could not be found > Cannot satisfy dependency: > From: RHAMT 4.2.0.Final (org.jboss.tools.windup.feature.feature.group 4.2.0.Final) > To: org.eclipse.equinox.p2.iu; org.jboss.tools.windup.model [4.2.0.Final,4.2.0.Final] > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26464) Relabel fabric8 analytics as dependency analytics in Central discovery

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26464?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26464: ------------------------------- Sprint: devex #159 December 2018, devex #164 April 2019 (was: devex #159 December 2018, devex #164 April 2019, devex #165 April 2019) > Relabel fabric8 analytics as dependency analytics in Central discovery > ---------------------------------------------------------------------- > > Key: JBIDE-26464 > URL: https://issues.jboss.org/browse/JBIDE-26464 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central-update > Affects Versions: 4.10.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.12.0.AM1 > > > Per discussion w/ Mickael Istria Bob Davis and Jeff MAURY, we should rename the Central connector for fabric8 analytics to match the new connector in Eclipse Marketplace (JBIDE-26463). -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ERT-722) [GTK4] Ensure snippets work on GTK4 [EBZ#545942]

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/ERT-722?page=com.atlassian.jira.plugin.sy... ] Jeff MAURY updated ERT-722: --------------------------- Sprint: devex #164 April 2019, devex #165 April 2019 (was: devex #164 April 2019) > [GTK4] Ensure snippets work on GTK4 [EBZ#545942] > ------------------------------------------------ > > Key: ERT-722 > URL: https://issues.jboss.org/browse/ERT-722 > Project: Eclipse Release Train > Issue Type: Task > Components: Platform > Reporter: Friendly Jira Robot > Assignee: Eric Williams > Priority: Major > Labels: SWT, bzira > > Make sure snippets behave as expected on GTK4. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 12 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 April 2019