March 2019 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26582) Add support for Quarkus based applications

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26582?page=com.atlassian.jira.plugi... ] André Dietisheim commented on JBIDE-26582: ------------------------------------------ [~jeffmaury] what is your vision for this support looking like? As far as I understood so far native images would only run on linux, but the dev-mode hotcode replace might be something that we can support? > Add support for Quarkus based applications > ------------------------------------------ > > Key: JBIDE-26582 > URL: https://issues.jboss.org/browse/JBIDE-26582 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.11.0.Final > Reporter: Jeff MAURY > Priority: Major > Fix For: 4.12.0.Final > > > We should support JBoss Tools based inner loop for Quarkus based applications. > In the first time support only OpenJDK based deployments as I'm not sure native image based deployments can support inner loop. > That would also probably means an update of the openJDK base image -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26599) LiveReload does not work with OpenShift3 server adapter

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26599?page=com.atlassian.jira.plugi... ] André Dietisheim commented on JBIDE-26599: ------------------------------------------ 4.11.Final shipped, we went out of time for this unfortunately. Postponing. > LiveReload does not work with OpenShift3 server adapter > ------------------------------------------------------- > > Key: JBIDE-26599 > URL: https://issues.jboss.org/browse/JBIDE-26599 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload, openshift > Affects Versions: 4.11.0.Final > Environment: oc cluster up 3.11 from Fedora repo > Openshift templates from: https://github.com/jboss-container-images/jboss-eap-7-openshift-image/tre... > Devstudio + installed livereload: > Version: 12.11.0.GA > Build id: GA-v20190321-1925-B4244 > Build date: 20190321-1925 > JDK 11.02 + F29 > Reporter: Josef Kopriva > Priority: Critical > Fix For: 4.12.0.AM1 > > Attachments: image-2019-03-27-10-30-34-801.png > > > If I try to directly connect to livereload server there is an error message: > {code:java} > HTTP ERROR 500 > Problem accessing /. Reason: > Server Error > Caused by: > java.lang.IllegalArgumentException: Invalid URI host: null (authority: null) > at org.eclipse.jetty.client.HttpClient.checkHost(HttpClient.java:506) > at org.eclipse.jetty.client.HttpClient.newHttpRequest(HttpClient.java:491) > at org.eclipse.jetty.client.HttpClient.newRequest(HttpClient.java:449) > at org.eclipse.jetty.client.HttpClient.newRequest(HttpClient.java:438) > at org.eclipse.jetty.proxy.AsyncMiddleManServlet.service(AsyncMiddleManServlet.java:92) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:873) > at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:542) > at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255) > at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1701) > at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255) > at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1345) > at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203) > at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:480) > at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1668) > at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201) > at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1247) > at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144) > at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) > at org.eclipse.jetty.server.Server.handle(Server.java:502) > at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:370) > at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:267) > at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:305) > at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103) > at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:117) > at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:765) > at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:683) > at java.base/java.lang.Thread.run(Thread.java:834) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26599) LiveReload does not work with OpenShift3 server adapter

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26599?page=com.atlassian.jira.plugi... ] André Dietisheim updated JBIDE-26599: ------------------------------------- Fix Version/s: 4.12.0.AM1 (was: 4.11.0.Final) > LiveReload does not work with OpenShift3 server adapter > ------------------------------------------------------- > > Key: JBIDE-26599 > URL: https://issues.jboss.org/browse/JBIDE-26599 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload, openshift > Affects Versions: 4.11.0.Final > Environment: oc cluster up 3.11 from Fedora repo > Openshift templates from: https://github.com/jboss-container-images/jboss-eap-7-openshift-image/tre... > Devstudio + installed livereload: > Version: 12.11.0.GA > Build id: GA-v20190321-1925-B4244 > Build date: 20190321-1925 > JDK 11.02 + F29 > Reporter: Josef Kopriva > Priority: Critical > Fix For: 4.12.0.AM1 > > Attachments: image-2019-03-27-10-30-34-801.png > > > If I try to directly connect to livereload server there is an error message: > {code:java} > HTTP ERROR 500 > Problem accessing /. Reason: > Server Error > Caused by: > java.lang.IllegalArgumentException: Invalid URI host: null (authority: null) > at org.eclipse.jetty.client.HttpClient.checkHost(HttpClient.java:506) > at org.eclipse.jetty.client.HttpClient.newHttpRequest(HttpClient.java:491) > at org.eclipse.jetty.client.HttpClient.newRequest(HttpClient.java:449) > at org.eclipse.jetty.client.HttpClient.newRequest(HttpClient.java:438) > at org.eclipse.jetty.proxy.AsyncMiddleManServlet.service(AsyncMiddleManServlet.java:92) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:873) > at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:542) > at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255) > at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1701) > at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255) > at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1345) > at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203) > at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:480) > at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1668) > at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201) > at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1247) > at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144) > at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) > at org.eclipse.jetty.server.Server.handle(Server.java:502) > at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:370) > at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:267) > at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:305) > at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103) > at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:117) > at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:765) > at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:683) > at java.base/java.lang.Thread.run(Thread.java:834) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4756) Cannot start devstudio on mac os with jdk 11

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBDS-4756?page=com.atlassian.jira.plugin.... ] Ondrej Dockal edited comment on JBDS-4756 at 3/28/19 5:01 PM: -------------------------------------------------------------- I tried myself on the CCI mac (bigmek). Installation with jdk 11 went alright, but when trying to run the devstudio I gotthe same message. My guess is that this is caused by slow network access to jdk which resides on shared drive. (/qa/tools). I will validate my assumptions... was (Author: odockal): I tried myself on the CCI mac (bigmek). Installation with jdk 11 went alright, but when trying to run the devstudio I gotthe same message. My guess is that this is caused by slow network access to jdk which resides on shared drive. (/qa/tools). I will my validate my assumptions... > Cannot start devstudio on mac os with jdk 11 > -------------------------------------------- > > Key: JBDS-4756 > URL: https://issues.jboss.org/browse/JBDS-4756 > Project: Red Hat CodeReady Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 12.11.0.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Fix For: 12.11.0.GA > > Attachments: Screenshot_20190204_115602.png > > > I can easily install devstudio on mac os with default jdk 11 (from /qa/tools/opt/osx/jdk11_last) but I cannot make it start. No other errors or warnings except the one here: > !Screenshot_20190204_115602.png|thumbnail! > More info links [here|https://support.apple.com/kb/DL1572?locale=en_US]. > I can also see installer [tests|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/D...] failures on mac os 10.12 and 10.13 with this tack trace: > {code} > java.awt.HeadlessException > at java.desktop/sun.awt.HeadlessToolkit.getScreenSize(HeadlessToolkit.java:186) > at org.netbeans.jemmy.util.PNGEncoder.captureScreen(PNGEncoder.java:244) > at org.netbeans.jemmy.util.PNGEncoder.captureScreen(PNGEncoder.java:237) > at com.jboss.jbds.installer.test.InstallerTest.testInstall(InstallerTest.java:49) > 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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) > at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:119) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:101) > 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.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103) > at com.sun.proxy.$Proxy0.invoke(Unknown Source) > at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150) > at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69) > {code} > It might be possible to at least to try the installation and run on some bare metal to verify this error. Could someone possibly assist here, please? I have a suspicion that it might be performance related as the time needed to even open the jdk folder on the shared drive takes quite some time. Thanks! -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-721) Create/update intern presentations

by Eric Williams (Jira)

Eric Williams created ERT-721: --------------------------------- Summary: Create/update intern presentations Key: ERT-721 URL: https://issues.jboss.org/browse/ERT-721 Project: Eclipse Release Train Issue Type: Task Reporter: Eric Williams Assignee: Eric Williams Work on intern committee related presentations/training materials. Update and review team talk with Xi. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26598) Unable to connect to "local" JMX process when instance launched with JDK 11

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBIDE-26598?page=com.atlassian.jira.plugi... ] Ondrej Dockal commented on JBIDE-26598: --------------------------------------- Initial issue https://www.oracle.com/technetwork/java/javase/9-removed-features-3745614.... > Unable to connect to "local" JMX process when instance launched with JDK 11 > --------------------------------------------------------------------------- > > Key: JBIDE-26598 > URL: https://issues.jboss.org/browse/JBIDE-26598 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.11.0.Final > Reporter: Aurélien Pupier > Priority: Blocker > Fix For: 4.11.0.Final > > > {code} > org.jboss.tools.jmx.local > Error > Wed Mar 27 09:25:29 CET 2019 > Unable to connect to jvm > org.jboss.tools.jmx.jvmmonitor.core.JvmCoreException: Could not get JMX service URL (PID: 9470) > at org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm.initialize(ActiveJvm.java:462) > at org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm.initialize(ActiveJvm.java:445) > at org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm.connect(ActiveJvm.java:233) > at org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm.connect(ActiveJvm.java:213) > at org.jboss.tools.jmx.local.internal.JvmConnectionWrapper.connect(JvmConnectionWrapper.java:118) > at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26601) Update hibernate tools dependency of org.jboss.tools.hibernate.runtime.v_5_4 to version 5.4.2.Final

by Koen Aers (Jira)

[ https://issues.jboss.org/browse/JBIDE-26601?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-26601: ------------------------------ Fix Version/s: 4.12.0.AM1 > Update hibernate tools dependency of org.jboss.tools.hibernate.runtime.v_5_4 to version 5.4.2.Final > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-26601 > URL: https://issues.jboss.org/browse/JBIDE-26601 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.11.0.Final > Reporter: Koen Aers > Priority: Major > Fix For: 4.12.0.AM1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26601) Update hibernate tools dependency of org.jboss.tools.hibernate.runtime.v_5_4 to version 5.4.2.Final

by Koen Aers (Jira)

[ https://issues.jboss.org/browse/JBIDE-26601?page=com.atlassian.jira.plugi... ] Koen Aers reassigned JBIDE-26601: --------------------------------- Assignee: Koen Aers > Update hibernate tools dependency of org.jboss.tools.hibernate.runtime.v_5_4 to version 5.4.2.Final > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-26601 > URL: https://issues.jboss.org/browse/JBIDE-26601 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.11.0.Final > Reporter: Koen Aers > Assignee: Koen Aers > Priority: Major > Fix For: 4.12.0.AM1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26601) Update hibernate tools dependency of org.jboss.tools.hibernate.runtime.v_5_4 to version 5.4.2.Final

by Koen Aers (Jira)

[ https://issues.jboss.org/browse/JBIDE-26601?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-26601: ------------------------------ Component/s: hibernate > Update hibernate tools dependency of org.jboss.tools.hibernate.runtime.v_5_4 to version 5.4.2.Final > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-26601 > URL: https://issues.jboss.org/browse/JBIDE-26601 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.11.0.Final > Reporter: Koen Aers > Priority: Major > Fix For: 4.12.0.AM1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26601) Update hibernate tools dependency of org.jboss.tools.hibernate.runtime.v_5_4 to version 5.4.2.Final

by Koen Aers (Jira)

[ https://issues.jboss.org/browse/JBIDE-26601?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-26601: ------------------------------ Affects Version/s: 4.11.0.Final > Update hibernate tools dependency of org.jboss.tools.hibernate.runtime.v_5_4 to version 5.4.2.Final > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-26601 > URL: https://issues.jboss.org/browse/JBIDE-26601 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.11.0.Final > Reporter: Koen Aers > Priority: Major > Fix For: 4.12.0.AM1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 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 March 2019