April 2020 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-27154) Update WildFly to version 19 in livereload itests

by Jeff MAURY (Jira)

[ https://issues.redhat.com/browse/JBIDE-27154?page=com.atlassian.jira.plug... ] Jeff MAURY updated JBIDE-27154: ------------------------------- Fix Version/s: 4.15.0.Final (was: 4.15.0.AM1) > Update WildFly to version 19 in livereload itests > ------------------------------------------------- > > Key: JBIDE-27154 > URL: https://issues.redhat.com/browse/JBIDE-27154 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests > Affects Versions: 4.15.0.AM1 > Reporter: Zbyněk Červinka > Assignee: Zbyněk Červinka > Priority: Major > Fix For: 4.15.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27084) Add proxy support for odo based explorer

by Jeff MAURY (Jira)

[ https://issues.redhat.com/browse/JBIDE-27084?page=com.atlassian.jira.plug... ] Jeff MAURY updated JBIDE-27084: ------------------------------- Fix Version/s: 4.15.0.Final (was: 4.15.0.AM1) > Add proxy support for odo based explorer > ---------------------------------------- > > Key: JBIDE-27084 > URL: https://issues.redhat.com/browse/JBIDE-27084 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.14.0.Final > Reporter: Jeff MAURY > Priority: Major > Fix For: 4.15.0.Final > > > We should add proxy support for the odo based explorer. This requires to set up HTTPS_PROXY env variable when launching odo if proxy is required for the cluster url. > I would recommand the following changes: > * OpenShiftClient should be now private to the OdoCli > * Modify Odo interface so as to remove the OpenShiftClient from the parameters > * Add a new reset method to Odo interface that will be called when the context is reset or add a new OdoFactory that will be called when context is reset. We will allocate the OpenShiftClient here and compute the HTTP_PROXY env variable if proxy is required for this cluster > * Modify odo launch calls so as to pass this env var each time odo is launched -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27086) Update WildFly version in examples.itests to version 19

by Jeff MAURY (Jira)

[ https://issues.redhat.com/browse/JBIDE-27086?page=com.atlassian.jira.plug... ] Jeff MAURY updated JBIDE-27086: ------------------------------- Fix Version/s: 4.15.0.Final (was: 4.15.0.AM1) > Update WildFly version in examples.itests to version 19 > ------------------------------------------------------- > > Key: JBIDE-27086 > URL: https://issues.redhat.com/browse/JBIDE-27086 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: project-examples > Affects Versions: 4.15.0.AM1 > Reporter: Zbyněk Červinka > Assignee: Zbyněk Červinka > Priority: Major > Fix For: 4.15.0.Final > > > - update WF to version 19 in examples.itests (server, blacklists) > - test the new examples and update JIRAs with the WF issues -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27085) Add artificatId validation in Quarkus wizard

by Jeff MAURY (Jira)

[ https://issues.redhat.com/browse/JBIDE-27085?page=com.atlassian.jira.plug... ] Jeff MAURY updated JBIDE-27085: ------------------------------- Fix Version/s: 4.15.0.Final (was: 4.15.0.AM1) > Add artificatId validation in Quarkus wizard > -------------------------------------------- > > Key: JBIDE-27085 > URL: https://issues.redhat.com/browse/JBIDE-27085 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: quarkus > Reporter: Oleksii Korniienko > Priority: Major > Fix For: 4.15.0.Final > > Attachments: Screenshot from 2020-03-05 14-36-10.png > > > project name and artifact id "testProjectGradle" is an Error: > !SUBENTRY 1 org.jboss.tools.foundation.core 4 0 2020-03-05 14:21:10.072 > !MESSAGE org.eclipse.ecf.filetransfer.IncomingFileTransferException: HttpComponents connection error response code 400. > !STACK 1 > org.eclipse.ecf.filetransfer.IncomingFileTransferException: HttpComponents connection error response code 400. > at org.eclipse.ecf.provider.filetransfer.httpclient45.HttpClientRetrieveFileTransfer.openStreams(HttpClientRetrieveFileTransfer.java:613) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:885) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:576) > at org.eclipse.ecf.provider.filetransfer.retrieve.MultiProtocolRetrieveAdapter.sendRetrieveRequest(MultiProtocolRetrieveAdapter.java:106) > at org.jboss.tools.foundation.core.ecf.internal.InternalURLTransport.transfer(InternalURLTransport.java:379) > at org.jboss.tools.foundation.core.ecf.internal.InternalURLTransport.performDownload(InternalURLTransport.java:332) > at org.jboss.tools.foundation.core.ecf.internal.InternalURLTransport.download(InternalURLTransport.java:262) > at org.jboss.tools.foundation.core.ecf.internal.InternalURLTransport.download(InternalURLTransport.java:243) > at org.jboss.tools.foundation.core.ecf.URLTransportUtility$3.run(URLTransportUtility.java:325) > at org.jboss.tools.foundation.core.jobs.BarrierProgressWaitJob.run(BarrierProgressWaitJob.java:85) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63) > !SUBENTRY 2 org.eclipse.ecf.identity 4 0 2020-03-05 14:21:10.072 > !MESSAGE HttpComponents connection error response code 400. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27083) Process management for running odo cli instances

by Jeff MAURY (Jira)

[ https://issues.redhat.com/browse/JBIDE-27083?page=com.atlassian.jira.plug... ] Jeff MAURY updated JBIDE-27083: ------------------------------- Fix Version/s: 4.15.0.Final (was: 4.15.0.AM1) > Process management for running odo cli instances > ------------------------------------------------ > > Key: JBIDE-27083 > URL: https://issues.redhat.com/browse/JBIDE-27083 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.14.0.Final > Reporter: Jeff MAURY > Assignee: Stephane Bouchet > Priority: Major > Fix For: 4.15.0.Final > > > While working on the odo based explorer to JBoss Tools, I noticed that we are starting long running process and those processes are not managed / controlled once launched. > I think we should do and I will explain my proposition. > The long processes are the following: > * watch > * follow log > * debug > Less critical , we also have describe, list services and component and in general each time we launch odo in a terminal. This is less critical because they are less long living. > The problem that we have is: > * we should stop them when context is switched > * we should stop them when tooling stops (seems VSCode is handling that properly) > * we should stop them when we undeploy/delete a component > Another plus is that managing them will prevent multiple executions of the same task and control of state for the debug. > Here is my proposition: each time we start a long running process we keep it at the OdoCli (for JBoss Tools / IJ) level in a map that is keyed by project / application / component / action-type. > Then, we can: > * while processing delete / undeploy, scan the map to find proper processes to stop > * while processing debug we can check that debug is already running or not > * for cleanup before tooling exit or context switch we should add a reset method (this is required btw for proxy support as we need to recompute the HTTPS_PROXY env variable that will be passed to future odo executions -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27088) Fix strings in Server ITests

by Jeff MAURY (Jira)

[ https://issues.redhat.com/browse/JBIDE-27088?page=com.atlassian.jira.plug... ] Jeff MAURY updated JBIDE-27088: ------------------------------- Fix Version/s: 4.15.0.Final (was: 4.15.0.AM1) > Fix strings in Server ITests > ---------------------------- > > Key: JBIDE-27088 > URL: https://issues.redhat.com/browse/JBIDE-27088 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests, server > Affects Versions: 4.14.0.Final > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Priority: Major > Fix For: 4.15.0.Final > > > Tests are failing with messages like this: > Item JBoss EAP 7.0.0 does not exist in table > org.eclipse.reddeer.core.exception.CoreLayerException: Item JBoss EAP 7.0.0 does not exist in table > at org.jboss.tools.as.ui.bot.itests.parametized.server.ServerRuntimesTest.acquireAndDetect(ServerRuntimesTest.java:136) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27093) Quarkus application.properties should be open with Generic text editor by default

by Jeff MAURY (Jira)

[ https://issues.redhat.com/browse/JBIDE-27093?page=com.atlassian.jira.plug... ] Jeff MAURY updated JBIDE-27093: ------------------------------- Fix Version/s: 4.15.0.Final (was: 4.15.0.AM1) > Quarkus application.properties should be open with Generic text editor by default > --------------------------------------------------------------------------------- > > Key: JBIDE-27093 > URL: https://issues.redhat.com/browse/JBIDE-27093 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: quarkus > Affects Versions: 4.14.0.Final > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.15.0.Final > > > Content assist for application.properties in quarkus project is working in VS Code, we should consider adding this feature in JBoss Tools. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27117) Update WildFly version in maven.itests to version 19

by Jeff MAURY (Jira)

[ https://issues.redhat.com/browse/JBIDE-27117?page=com.atlassian.jira.plug... ] Jeff MAURY updated JBIDE-27117: ------------------------------- Fix Version/s: 4.15.0.Final (was: 4.15.0.AM1) > Update WildFly version in maven.itests to version 19 > ---------------------------------------------------- > > Key: JBIDE-27117 > URL: https://issues.redhat.com/browse/JBIDE-27117 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: maven > Affects Versions: 4.15.0.AM1 > Reporter: Zbyněk Červinka > Assignee: Zbyněk Červinka > Priority: Major > Fix For: 4.15.0.Final > > > - update WF to version 19 in maven.itests -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 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 April 2020