March 2019 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26568) Add WF16 and EAP72 in ITests suite

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26568?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-26568. --------------------------------- Resolution: Done Pr is merged. Closing. > Add WF16 and EAP72 in ITests suite > ---------------------------------- > > Key: JBIDE-26568 > URL: https://issues.jboss.org/browse/JBIDE-26568 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, server > Affects Versions: 4.11.0.Final > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Priority: Major > Fix For: 4.11.0.Final > > > Support for WildFly 16 and EAP 7.2 have been added, we need to update ITests. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ERT-698) [GTK4] Remove style property accessors [EBZ#543806]

by Eric Williams (Jira)

[ https://issues.jboss.org/browse/ERT-698?page=com.atlassian.jira.plugin.sy... ] Eric Williams resolved ERT-698. ------------------------------- Resolution: Done > [GTK4] Remove style property accessors [EBZ#543806] > --------------------------------------------------- > > Key: ERT-698 > URL: https://issues.jboss.org/browse/ERT-698 > Project: Eclipse Release Train > Issue Type: Task > Components: Platform > Reporter: Friendly Jira Robot > Assignee: Eric Williams > Priority: Major > Labels: SWT, bzira > > gtk_widget_style_get() is gone on GTK4 and needs to be removed/replaced with proper GTK CSS or GtkStyleContext functions. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26562) debugging does not work for eap-cd-basic-s2i template from CRC

by Snjezana Peco (Jira)

[ https://issues.jboss.org/browse/JBIDE-26562?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-26562: --------------------------------------- [~adietish] Have you solved the issue? > debugging does not work for eap-cd-basic-s2i template from CRC > -------------------------------------------------------------- > > Key: JBIDE-26562 > URL: https://issues.jboss.org/browse/JBIDE-26562 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift, server > Affects Versions: 4.11.0.AM1 > Environment: F29, devstudio AM1-v20190221-1020-B4114, CDK v3.8.0-alpha.1-1 > Reporter: Josef Kopriva > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.11.0.Final > > Attachments: image-2019-02-26-10-19-19-366.png, image-2019-03-14-16-30-04-450.png, image-2019-03-18-12-06-33-851.png > > > Restarting server adapter in debug for openshift application results in not responding job *Enabling "openshift maven profile"*: !image-2019-02-26-10-19-19-366.png|thumbnail! -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26562) debugging does not work for eap-cd-basic-s2i template from CRC

by Andre Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26562?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-26562: ------------------------------------------ [~snjeza] Thx for chiming in, I just found the issue with the help of [~rob.stryker] I think. The problem was 2-fold: * The server launch controller was joining with a job that would activate a maven profile. The maven job being locked out by concurrent build jobs made the launcher stuck waiting. * the maven profile activation job was not requesting the workspace lock (via scheduling rules) right away. It just got stalled waiting for concurrent workspace build jobs to release the workspace lock. > debugging does not work for eap-cd-basic-s2i template from CRC > -------------------------------------------------------------- > > Key: JBIDE-26562 > URL: https://issues.jboss.org/browse/JBIDE-26562 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift, server > Affects Versions: 4.11.0.AM1 > Environment: F29, devstudio AM1-v20190221-1020-B4114, CDK v3.8.0-alpha.1-1 > Reporter: Josef Kopriva > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.11.0.Final > > Attachments: image-2019-02-26-10-19-19-366.png, image-2019-03-14-16-30-04-450.png, image-2019-03-18-12-06-33-851.png > > > Restarting server adapter in debug for openshift application results in not responding job *Enabling "openshift maven profile"*: !image-2019-02-26-10-19-19-366.png|thumbnail! -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ERT-717) [GTK3] MouseWheel event only reports GDK.GDK_SCROLL_UP [EBZ#545403]

by Eric Williams (Jira)

[ https://issues.jboss.org/browse/ERT-717?page=com.atlassian.jira.plugin.sy... ] Eric Williams resolved ERT-717. ------------------------------- Resolution: Done > [GTK3] MouseWheel event only reports GDK.GDK_SCROLL_UP [EBZ#545403] > ------------------------------------------------------------------- > > Key: ERT-717 > URL: https://issues.jboss.org/browse/ERT-717 > Project: Eclipse Release Train > Issue Type: Task > Components: Platform > Reporter: Friendly Jira Robot > Assignee: Eric Williams > Priority: Major > Labels: SWT, bzira > > Created attachment 277864 > Snippet to reproduce > When executing the attached snippet on CentOS 7.6 (GTK 3.22.30, Adwaita theme) using SWT v4926r2, and scrolling the mouse wheel over the shells content area, it will print 3, no matter whether you scroll the wheel up or down. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26578) org.jboss.tools.openshift.ui fails to load

by Jeff MAURY (Jira)

Jeff MAURY created JBIDE-26578: ---------------------------------- Summary: org.jboss.tools.openshift.ui fails to load Key: JBIDE-26578 URL: https://issues.jboss.org/browse/JBIDE-26578 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.11.0.AM1 Reporter: Jeff MAURY Assignee: Jeff MAURY Fix For: 4.11.0.Final The bundle fails to load with this error: {code:java} !ENTRY org.jboss.tools.openshift.ui 4 0 2019-03-18 18:56:49.104 !MESSAGE FrameworkEvent ERROR !STACK 0 org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.openshift.ui [1088] Bundle was not resolved because of a uses constraint violation. org.apache.felix.resolver.reason.ReasonException: Uses constraint violation. Unable to resolve resource org.jboss.tools.openshift.ui [osgi.identity; type="osgi.bundle"; version:Version="3.6.0.v20190220-1733"; osgi.identity="org.jboss.tools.openshift.ui"; singleton:="true"] because it is exposed to package 'javax.xml.bind.annotation' from resources org.eclipse.osgi [osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.13.300.v20190218-1622"; singleton:="true"] and javax.xml.bind [osgi.identity; type="osgi.bundle"; version:Version="2.2.0.v201105210648"; osgi.identity="javax.xml.bind"] via two dependency chains. {code:java} Chain 1: org.jboss.tools.openshift.ui [osgi.identity; type="osgi.bundle"; version:Version="3.6.0.v20190220-1733"; osgi.identity="org.jboss.tools.openshift.ui"; singleton:="true"] require: (osgi.wiring.bundle=org.eclipse.core.runtime) | provide: osgi.wiring.bundle: org.eclipse.core.runtime org.eclipse.osgi [osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.13.300.v20190218-1622"; singleton:="true"] Chain 2: org.jboss.tools.openshift.ui [osgi.identity; type="osgi.bundle"; version:Version="3.6.0.v20190220-1733"; osgi.identity="org.jboss.tools.openshift.ui"; singleton:="true"] require: (&(osgi.wiring.bundle=com.spotify.docker.client)(bundle-version>=3.4.0)) | provide: osgi.wiring.bundle; bundle-version:Version="8.11.7.v20180731-1413"; osgi.wiring.bundle="com.spotify.docker.client" com.spotify.docker.client [osgi.identity; type="osgi.bundle"; version:Version="8.11.7.v20180731-1413"; osgi.identity="com.spotify.docker.client"] import: (&(osgi.wiring.package=javax.ws.rs)(version>=2.0.0)) | export: osgi.wiring.package=javax.ws.rs; uses:=javax.xml.bind.annotation javax.ws.rs [osgi.identity; type="osgi.bundle"; version:Version="2.0.1.v201504171603"; osgi.identity="javax.ws.rs"] import: (&(osgi.wiring.package=javax.xml.bind.annotation)(&(version>=2.2.0)(!(version>=3.0.0)))) | export: osgi.wiring.package: javax.xml.bind.annotation javax.xml.bind [osgi.identity; type="osgi.bundle"; version:Version="2.2.0.v201105210648"; osgi.identity="javax.xml.bind"] at org.eclipse.osgi.container.Module.start(Module.java:452) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1784) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1763) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1726) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1657) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:233) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:343) {code} This does not happen with Java11. This seems to be cause because org.eclipse.osgi exports javax.xml.bind packages and the new Docker stuff is requesting a specific version of javax.xml.bind thus we have two versions of the packages. Solution is to replace require bundle org.eclipse.core.runtime by import package -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26570) WildFly 15 and 16 do not allow JEE8 deployments

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26570?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26570: ------------------------------- Fix Version/s: 4.11.0.Final Sprint: devex #163 March 2019 > WildFly 15 and 16 do not allow JEE8 deployments > ----------------------------------------------- > > Key: JBIDE-26570 > URL: https://issues.jboss.org/browse/JBIDE-26570 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Emond Papegaaij > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.11.0.Final > > > This issue seems to be the same as I reported before for WildFly 14: JBIDE-26390. I'm getting the same error trying to deploy a JEE8 ear on WildFly 15 and 16. My version of JBoss AS, WildFly & EAP Server Tools is 3.6.2.v20190304-1841. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26570) WildFly 15 and 16 do not allow JEE8 deployments

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26570?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-26570: ---------------------------------- Assignee: Jeff MAURY (was: Rob Stryker) > WildFly 15 and 16 do not allow JEE8 deployments > ----------------------------------------------- > > Key: JBIDE-26570 > URL: https://issues.jboss.org/browse/JBIDE-26570 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Emond Papegaaij > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.11.0.Final > > > This issue seems to be the same as I reported before for WildFly 14: JBIDE-26390. I'm getting the same error trying to deploy a JEE8 ear on WildFly 15 and 16. My version of JBoss AS, WildFly & EAP Server Tools is 3.6.2.v20190304-1841. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26562) debugging does not work for eap-cd-basic-s2i template from CRC

by Snjezana Peco (Jira)

[ https://issues.jboss.org/browse/JBIDE-26562?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-26562: --------------------------------------- [~adietish] I will try to find the cause of the issue. > debugging does not work for eap-cd-basic-s2i template from CRC > -------------------------------------------------------------- > > Key: JBIDE-26562 > URL: https://issues.jboss.org/browse/JBIDE-26562 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift, server > Affects Versions: 4.11.0.AM1 > Environment: F29, devstudio AM1-v20190221-1020-B4114, CDK v3.8.0-alpha.1-1 > Reporter: Josef Kopriva > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.11.0.Final > > Attachments: image-2019-02-26-10-19-19-366.png, image-2019-03-14-16-30-04-450.png, image-2019-03-18-12-06-33-851.png > > > Restarting server adapter in debug for openshift application results in not responding job *Enabling "openshift maven profile"*: !image-2019-02-26-10-19-19-366.png|thumbnail! -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26562) debugging does not work for eap-cd-basic-s2i template from CRC

by Andre Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26562?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-26562: ------------------------------------------ here's a full dump of all threads via jstack: https://paste.fedoraproject.org/paste/CvmQGpQd9QbHtfTrp995bQ [~snjeza] could you please have a look into this? I'd appreciate your help a lot, I have no clue what's blocking here tbh. > debugging does not work for eap-cd-basic-s2i template from CRC > -------------------------------------------------------------- > > Key: JBIDE-26562 > URL: https://issues.jboss.org/browse/JBIDE-26562 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift, server > Affects Versions: 4.11.0.AM1 > Environment: F29, devstudio AM1-v20190221-1020-B4114, CDK v3.8.0-alpha.1-1 > Reporter: Josef Kopriva > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.11.0.Final > > Attachments: image-2019-02-26-10-19-19-366.png, image-2019-03-14-16-30-04-450.png, image-2019-03-18-12-06-33-851.png > > > Restarting server adapter in debug for openshift application results in not responding job *Enabling "openshift maven profile"*: !image-2019-02-26-10-19-19-366.png|thumbnail! -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 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 March 2019