May 2020 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-27272) Prepare Openshift 4.4 cluster for testing

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-27272?page=com.atlassian.jira.plug... ] Josef Kopriva closed JBIDE-27272. --------------------------------- Resolution: Done > Prepare Openshift 4.4 cluster for testing > ----------------------------------------- > > Key: JBIDE-27272 > URL: https://issues.redhat.com/browse/JBIDE-27272 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.16.0.AM1 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Priority: Major > Fix For: 4.16.0.AM1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27284) OpenShift ODO View: wrong label in Create component wizard

by Josef Kopriva (Jira)

Josef Kopriva created JBIDE-27284: ------------------------------------- Summary: OpenShift ODO View: wrong label in Create component wizard Key: JBIDE-27284 URL: https://issues.redhat.com/browse/JBIDE-27284 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.16.0.AM1 Reporter: Josef Kopriva Attachments: image-2020-05-21-12-06-17-521.png !image-2020-05-21-12-06-17-521.png|thumbnail! There should be something else like: "Create component" or "Component details" or "Component parameters" -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27283) Run configuration seems to trigger build for all projects

by Falko Modler (Jira)

[ https://issues.redhat.com/browse/JBIDE-27283?page=com.atlassian.jira.plug... ] Falko Modler updated JBIDE-27283: --------------------------------- Description: I have over 100 different projects in my default Eclipse workspace and usually "Build automatically" is off (for obvious reasons). When I execute the "Quarkus Application" run config for a tiny Quarkus example project I often have to wait until unrelated projects are build (judging from the output of the progress monitor). This is annoying and seems very unnecessary. It would come in handy to have something like in the attached screenshot. was: I have over 100 different projects in my default Eclipse workspace and usually "Build automatically" is off (for obvious reasons). When I execute the "Quarkus Application" run config for a tiny Quarkus example project I often have to wait until unrelated projects are build (judging from the output of the progress monitor). This is annoying and seems very unnecessary. It would come in handy to have somthing like in the attached screenshot. > Run configuration seems to trigger build for all projects > --------------------------------------------------------- > > Key: JBIDE-27283 > URL: https://issues.redhat.com/browse/JBIDE-27283 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: quarkus > Affects Versions: 4.15.0.Final > Reporter: Falko Modler > Priority: Major > Attachments: build_before_launch.PNG > > > I have over 100 different projects in my default Eclipse workspace and usually "Build automatically" is off (for obvious reasons). > When I execute the "Quarkus Application" run config for a tiny Quarkus example project I often have to wait until unrelated projects are build (judging from the output of the progress monitor). > This is annoying and seems very unnecessary. > It would come in handy to have something like in the attached screenshot. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27283) Run configuration seems to trigger build for all projects

by Falko Modler (Jira)

Falko Modler created JBIDE-27283: ------------------------------------ Summary: Run configuration seems to trigger build for all projects Key: JBIDE-27283 URL: https://issues.redhat.com/browse/JBIDE-27283 Project: Tools (JBoss Tools) Issue Type: Bug Components: quarkus Affects Versions: 4.15.0.Final Reporter: Falko Modler Attachments: build_before_launch.PNG I have over 100 different projects in my default Eclipse workspace and usually "Build automatically" is off (for obvious reasons). When I execute the "Quarkus Application" run config for a tiny Quarkus example project I often have to wait until unrelated projects are build (judging from the output of the progress monitor). This is annoying and seems very unnecessary. It would come in handy to have somthing like in the attached screenshot. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27186) Quarkus Tools- Debugger failed to attach: handshake failed - connection prematurally closed

by Oleksii Korniienko (Jira)

[ https://issues.redhat.com/browse/JBIDE-27186?page=com.atlassian.jira.plug... ] Oleksii Korniienko closed JBIDE-27186. -------------------------------------- Closing. Tested with: Red Hat CodeReady Studio Version: 12.16.0.AM1 Build id: AM1-v20200518-0713-B6398 Build date: 20200518-0713 > Quarkus Tools- Debugger failed to attach: handshake failed - connection prematurally closed > ------------------------------------------------------------------------------------------- > > Key: JBIDE-27186 > URL: https://issues.redhat.com/browse/JBIDE-27186 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: quarkus > Affects Versions: 4.14.0.AM1 > Reporter: Daniele Tasinato > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.16.0.AM1 > > Attachments: image (2).png > > > [INFO] Compiling 4 source files to C:\Users\developer\Documents\findmagazine\findmagazine\target\classes > [INFO] > [INFO] --- quarkus-maven-plugin:1.3.1.Final:dev (default-cli) @ findmagazine --- > Listening for transport dt_socket at address: 5005 > {color:red}Debugger failed to attach: handshake failed - connection prematurally closed{color} > __ ____ __ _____ ___ __ ____ ______ > --/ __ \/ / / / _ | / _ \/ //_/ / / / __/ > -/ /_/ / /_/ / __ |/ , _/ ,< / /_/ /\ \ > --\___\_\____/_/ |_/_/|_/_/|_|\____/___/ > 2020-04-04 17:05:04,813 WARN [io.qua.agr.dep.AgroalProcessor] (build-7) The Agroal dependency is present but no JDBC datasources have been defined. > 2020-04-04 17:05:09,416 WARN [io.qua.net.run.NettyRecorder] (Thread-71) Localhost lookup took more than one second, you need to add a /etc/hosts entry to improve Quarkus startup time. On Windows the path is C:\Windows\System32\Drivers\etc\hosts. See https://thoeni.io/post/macos-sierra-java/ for macOS details. > 2020-04-04 17:05:09,455 INFO [io.qua.qua.run.QuartzScheduler] (main) No scheduled business methods found - Quartz scheduler will not be started > 2020-04-04 17:05:09,468 INFO [io.quarkus] (main) findmagazine 1.0.0-SNAPSHOT (powered by Quarkus 1.3.1.Final) started in 6.097s. Listening on: http://0.0.0.0:8080 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3089) x509 Authentication to OpenShift

by Jeff MAURY (Jira)

[ https://issues.redhat.com/browse/JBDS-3089?page=com.atlassian.jira.plugin... ] Jeff MAURY closed JBDS-3089. ---------------------------- > x509 Authentication to OpenShift > -------------------------------- > > Key: JBDS-3089 > URL: https://issues.redhat.com/browse/JBDS-3089 > Project: Red Hat CodeReady Studio (devstudio) > Issue Type: Feature Request > Components: openshift > Affects Versions: 8.0.0.Beta3 > Reporter: Eric Rich > Assignee: Jeff MAURY > Priority: Major > Labels: authentication, ssl > Fix For: LATER > > > Currently customers are asking for RHC to support x509 Authentication with the broker service (https://bugzilla.redhat.com/show_bug.cgi?id=1089703). The same is being asked of JBDS -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27186) Quarkus Tools- Debugger failed to attach: handshake failed - connection prematurally closed

by Jeff MAURY (Jira)

[ https://issues.redhat.com/browse/JBIDE-27186?page=com.atlassian.jira.plug... ] Jeff MAURY commented on JBIDE-27186: ------------------------------------ This is output from the JVM which I can't much. This cause because before launching the remote debugger in Eclipse, I try to establish a connection to port 5005 and the remote JVM now feels a debugger has connected. > Quarkus Tools- Debugger failed to attach: handshake failed - connection prematurally closed > ------------------------------------------------------------------------------------------- > > Key: JBIDE-27186 > URL: https://issues.redhat.com/browse/JBIDE-27186 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: quarkus > Affects Versions: 4.14.0.AM1 > Reporter: Daniele Tasinato > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.16.0.AM1 > > Attachments: image (2).png > > > [INFO] Compiling 4 source files to C:\Users\developer\Documents\findmagazine\findmagazine\target\classes > [INFO] > [INFO] --- quarkus-maven-plugin:1.3.1.Final:dev (default-cli) @ findmagazine --- > Listening for transport dt_socket at address: 5005 > {color:red}Debugger failed to attach: handshake failed - connection prematurally closed{color} > __ ____ __ _____ ___ __ ____ ______ > --/ __ \/ / / / _ | / _ \/ //_/ / / / __/ > -/ /_/ / /_/ / __ |/ , _/ ,< / /_/ /\ \ > --\___\_\____/_/ |_/_/|_/_/|_|\____/___/ > 2020-04-04 17:05:04,813 WARN [io.qua.agr.dep.AgroalProcessor] (build-7) The Agroal dependency is present but no JDBC datasources have been defined. > 2020-04-04 17:05:09,416 WARN [io.qua.net.run.NettyRecorder] (Thread-71) Localhost lookup took more than one second, you need to add a /etc/hosts entry to improve Quarkus startup time. On Windows the path is C:\Windows\System32\Drivers\etc\hosts. See https://thoeni.io/post/macos-sierra-java/ for macOS details. > 2020-04-04 17:05:09,455 INFO [io.qua.qua.run.QuartzScheduler] (main) No scheduled business methods found - Quartz scheduler will not be started > 2020-04-04 17:05:09,468 INFO [io.quarkus] (main) findmagazine 1.0.0-SNAPSHOT (powered by Quarkus 1.3.1.Final) started in 6.097s. Listening on: http://0.0.0.0:8080 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27280) EAP microprofile QS: microprofile-health wrong packaging

by Emmanuel Hugonnet (Jira)

[ https://issues.redhat.com/browse/JBIDE-27280?page=com.atlassian.jira.plug... ] Emmanuel Hugonnet commented on JBIDE-27280: ------------------------------------------- switching to packaging 'ejb' works too. > EAP microprofile QS: microprofile-health wrong packaging > -------------------------------------------------------- > > Key: JBIDE-27280 > URL: https://issues.redhat.com/browse/JBIDE-27280 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples, server > Affects Versions: 4.16.0.AM1 > Reporter: Josef Kopriva > Assignee: Robert Stryker > Priority: Major > > microprofile-health quickstart cannot be deployed to server until packaging in pom is changed from jar to war, afterwards it works as expected. > This seems to be as an upstream issue. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27208) Switch to Tycho 1.7.0

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-27208?page=com.atlassian.jira.plug... ] Stephane Bouchet updated JBIDE-27208: ------------------------------------- Fix Version/s: 4.16.0.AM1 (was: 4.16.0.Final) > Switch to Tycho 1.7.0 > --------------------- > > Key: JBIDE-27208 > URL: https://issues.redhat.com/browse/JBIDE-27208 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.15.0.AM1 > Reporter: Jeff MAURY > Assignee: Stephane Bouchet > Priority: Major > Fix For: 4.16.0.AM1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27282) OpenShift Explorer: login with credentials does not work for 4.5

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-27282?page=com.atlassian.jira.plug... ] Josef Kopriva updated JBIDE-27282: ---------------------------------- Steps to Reproduce: 1. Create OpenShift 4.5 cluster 2. Try to login to cluster with Username/Password for kubeadmin 3. An error is shown in error log and login dialog was: 1. Create OpenShift 4.5 cluster 2. Try to login to cluster with Username/Password 3. An error is shown in error log and login dialog > OpenShift Explorer: login with credentials does not work for 4.5 > ---------------------------------------------------------------- > > Key: JBIDE-27282 > URL: https://issues.redhat.com/browse/JBIDE-27282 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.16.0.AM1 > Reporter: Josef Kopriva > Priority: Critical > > {code:java} > eclipse.buildId=12.16.0.AM1-v20200520-0418-B6414 > java.version=11.0.7 > java.vendor=AdoptOpenJDK > BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_GB > Framework arguments: -product com.jboss.devstudio.core.product -keyring /Users/jkopriva/.eclipse_keyring > Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product com.jboss.devstudio.core.product -keyring /Users/jkopriva/.eclipse_keyring > org.jboss.tools.openshift.ui > Error > Wed May 20 09:09:18 CEST 2020 > Invalid character: < > java.lang.IllegalArgumentException: Invalid character: < > at org.jboss.dmr.JSONParserImpl.invalid(JSONParserImpl.java:136) > at org.jboss.dmr.JSONParser.yyLex(JSONParser.java:596) > at org.jboss.dmr.JSONParser.yyParse(JSONParser.java:662) > at org.jboss.dmr.ModelNode.fromJSONString(ModelNode.java:1472) > at com.openshift.internal.restclient.ApiTypeMapper.getApiGroups(ApiTypeMapper.java:225) > at com.openshift.internal.restclient.ApiTypeMapper.init(ApiTypeMapper.java:159) > at com.openshift.internal.restclient.ApiTypeMapper.isSupported(ApiTypeMapper.java:87) > at com.openshift.internal.restclient.URLBuilder.buildWithNamespaceInPath(URLBuilder.java:148) > at com.openshift.internal.restclient.URLBuilder.build(URLBuilder.java:135) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:301) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:274) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:242) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:225) > at com.openshift.internal.restclient.DefaultClient.get(DefaultClient.java:410) > at com.openshift.internal.restclient.authorization.AuthorizationContext.isAuthorized(AuthorizationContext.java:63) > at org.jboss.tools.openshift.core.connection.Connection.authorize(Connection.java:240) > at org.jboss.tools.openshift.core.connection.Connection.connect(Connection.java:229) > at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPageModel.connect(ConnectionWizardPageModel.java:300) > at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPage$ConnectJob.doRun(ConnectionWizardPage.java:434) > at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:37) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 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 May 2020