February 2020 - jbosstools-issues

[JBoss JIRA] (JBIDE-27022) Add Java EE example.itests to use Java EE 8 repo

by Zbyněk Červinka (Jira)

[ https://issues.redhat.com/browse/JBIDE-27022?page=com.atlassian.jira.plug... ] Zbyněk Červinka resolved JBIDE-27022. ------------------------------------- Resolution: Done Both PRs have been merged, I am resolving this JIRA. > Add Java EE example.itests to use Java EE 8 repo > ------------------------------------------------ > > Key: JBIDE-27022 > URL: https://issues.redhat.com/browse/JBIDE-27022 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: project-examples > Affects Versions: 4.14.0.AM1 > Reporter: Zbyněk Červinka > Assignee: Zbyněk Červinka > Priority: Minor > Fix For: 4.14.0.Final > > > Add profile and jobs to use Java EE example.itests to use Java EE 8 repo: https://github.com/javaee-samples/javaee8-samples -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-27022) Add Java EE example.itests to use Java EE 8 repo

by Zbyněk Červinka (Jira)

[ https://issues.redhat.com/browse/JBIDE-27022?page=com.atlassian.jira.plug... ] Zbyněk Červinka updated JBIDE-27022: ------------------------------------ Estimated Difficulty: Medium (was: Low) > Add Java EE example.itests to use Java EE 8 repo > ------------------------------------------------ > > Key: JBIDE-27022 > URL: https://issues.redhat.com/browse/JBIDE-27022 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: project-examples > Affects Versions: 4.14.0.AM1 > Reporter: Zbyněk Červinka > Assignee: Zbyněk Červinka > Priority: Minor > Fix For: 4.14.0.Final > > > Add profile and jobs to use Java EE example.itests to use Java EE 8 repo: https://github.com/javaee-samples/javaee8-samples -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-27019) Show in -> Web console option does not work at times

by Jeff MAURY (Jira)

[ https://issues.redhat.com/browse/JBIDE-27019?page=com.atlassian.jira.plug... ] Jeff MAURY updated JBIDE-27019: ------------------------------- Sprint: devex #179 Jan/Feb 2020, devex #180 Feb/Mar 2020 (was: devex #179 Jan/Feb 2020) > Show in -> Web console option does not work at times > ---------------------------------------------------- > > Key: JBIDE-27019 > URL: https://issues.redhat.com/browse/JBIDE-27019 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift > Affects Versions: 4.14.0.AM1 > Reporter: Ondrej Dockal > Assignee: André Dietisheim > Priority: Major > Fix For: 4.14.0.Final > > > Show in -> Web Console does not work for Openshift connection created from CRC 1.3 version as the Server's url (OS 4.2 endpoint - https://api.crc.testing:6443/) does not work for web console access. The correct one is https://console-openshift-console.apps-crc.testing/. > I got this error stack trace, btw: > {code} > eclipse.buildId=12.14.0.AM1-v20200123-0055-B5802 > java.version=11.0.5 > 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_12140AM1-0123/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > org.eclipse.core.jobs > Error > Mon Jan 27 15:12:23 CET 2020 > An internal error occurred during: "Retrieving console for https://api.crc.testing:6443...". > com.openshift.restclient.UnsupportedEndpointException: Unable to determine the api endpoint for kind 'ConfigMap' > at com.openshift.internal.restclient.URLBuilder.buildWithNamespaceInPath(URLBuilder.java:149) > at com.openshift.internal.restclient.URLBuilder.build(URLBuilder.java:135) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:297) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:271) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:239) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:222) > at com.openshift.internal.restclient.DefaultClient.get(DefaultClient.java:406) > at com.openshift.internal.restclient.capability.server.Console.getOpenShift4ConsoleUrl(Console.java:93) > at com.openshift.internal.restclient.capability.server.Console.getOpenShift4ConsoleUrl(Console.java:107) > at com.openshift.internal.restclient.capability.server.Console.getConsoleUrl(Console.java:64) > at org.jboss.tools.openshift.core.connection.Connection.getConsoleURL(Connection.java:381) > at org.jboss.tools.openshift.internal.ui.handler.OpenInWebConsoleHandler.lambda$0(OpenInWebConsoleHandler.java:61) > at org.eclipse.core.runtime.jobs.Job$1.run(Job.java:164) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-27023) JAXWS - Provider org.apache.axis2.jaxws.spi.Provider not found

by Jeff MAURY (Jira)

[ https://issues.redhat.com/browse/JBIDE-27023?page=com.atlassian.jira.plug... ] Jeff MAURY updated JBIDE-27023: ------------------------------- Sprint: devex #179 Jan/Feb 2020, devex #180 Feb/Mar 2020 (was: devex #179 Jan/Feb 2020) > JAXWS - Provider org.apache.axis2.jaxws.spi.Provider not found > -------------------------------------------------------------- > > Key: JBIDE-27023 > URL: https://issues.redhat.com/browse/JBIDE-27023 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.14.0.AM1 > Reporter: Ondrej Dockal > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.14.0.Final > > > javax.xml.ws.spi.FactoryFinder$ConfigurationError: Provider org.apache.axis2.jaxws.spi.Provider not found > {code} > !ENTRY org.eclipse.core.jobs 4 2 2020-01-28 18:43:13.650 > !MESSAGE An internal error occurred during: "NLS missing message: JAXRSWSTestView_Invoking_WS_Status in: org.jboss.tools.ws.ui.messages.JBossWSUI". > !STACK 0 > javax.xml.ws.spi.FactoryFinder$ConfigurationError: Provider org.apache.axis2.jaxws.spi.Provider not found > at javax.xml.ws.spi.FactoryFinder$2.run(FactoryFinder.java:135) > at javax.xml.ws.spi.FactoryFinder.doPrivileged(FactoryFinder.java:264) > at javax.xml.ws.spi.FactoryFinder.newInstance(FactoryFinder.java:123) > at javax.xml.ws.spi.FactoryFinder.access$2(FactoryFinder.java:112) > at javax.xml.ws.spi.FactoryFinder$3.run(FactoryFinder.java:255) > at javax.xml.ws.spi.FactoryFinder.doPrivileged(FactoryFinder.java:264) > at javax.xml.ws.spi.FactoryFinder.find(FactoryFinder.java:166) > at javax.xml.ws.spi.Provider.provider(Provider.java:39) > at javax.xml.ws.Service.<init>(Service.java:36) > at javax.xml.ws.Service.create(Service.java:116) > at org.jboss.tools.ws.jaxws.ui.tester.JAXWSTester2.doTest(JAXWSTester2.java:143) > at org.jboss.tools.ws.jaxws.ui.view.JAXWSType.handleWSTest(JAXWSType.java:113) > at org.jboss.tools.ws.ui.views.WebServicesTestView$16.run(WebServicesTestView.java:697) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-27026) Adjust Job DSL defined QE Jobs to be operational on RHEV Jenkins CSB Master

by Jeff MAURY (Jira)

[ https://issues.redhat.com/browse/JBIDE-27026?page=com.atlassian.jira.plug... ] Jeff MAURY updated JBIDE-27026: ------------------------------- Sprint: devex #179 Jan/Feb 2020, devex #180 Feb/Mar 2020 (was: devex #179 Jan/Feb 2020) > Adjust Job DSL defined QE Jobs to be operational on RHEV Jenkins CSB Master > --------------------------------------------------------------------------- > > Key: JBIDE-27026 > URL: https://issues.redhat.com/browse/JBIDE-27026 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Affects Versions: 4.14.0.Final > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Fix For: 4.14.0.Final > > > Please, update Job DSL defined QE jobs to be aligned with Jenkins CSB Master on RHEV. Especially testing matrices of OSes, other configuration tools - Java axes, Groovy or maven, credentials IDs, etc. > Your jobs defined in job dsl have to run on RHEV Jenkins. Seed job can be found on dev-platform-jenkins -> DSL Jobs seed -> cci-config-seed, once you are done adjusting your jobs, you can test locally using CCI-JD and then using seed to get it into Jenkins master. > Be aware that: > * former jenkins labels for OSes and jdks were different from labels defined jenkins using jcasc -> It should be fixed, but you still need to check > * You need to sync your credentials IDs (hardcoded in RHEV Jenkins could differ from jcasc defined) > * Matrix combination filter should be updated to something like: {code}(label =~ "mac") && !(jdk =~ "open") || !(label =~ "mac") && (jdk =~ "open"){code} > * [~jkopriva] is updating and extracting matrices (axes function in job dsl language) to be general and you just use constants of arrays for each axes, ie. OS = ['rhel', 'win'], JDK = ['java11', 'jdk-39'] > * After we have jobs running every component owner will disable former QE jobs and these will be erased in future -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-27039) OpenShift ODO view: in Login page password is not hidden

by Jeff MAURY (Jira)

[ https://issues.redhat.com/browse/JBIDE-27039?page=com.atlassian.jira.plug... ] Jeff MAURY updated JBIDE-27039: ------------------------------- Sprint: devex #179 Jan/Feb 2020, devex #180 Feb/Mar 2020 (was: devex #179 Jan/Feb 2020) > OpenShift ODO view: in Login page password is not hidden > -------------------------------------------------------- > > Key: JBIDE-27039 > URL: https://issues.redhat.com/browse/JBIDE-27039 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.14.0.Final > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.14.0.Final > > Attachments: image-2020-02-05-15-16-49-453.png > > > Password is not hidden in OpenShift View ODO login page: > !image-2020-02-05-15-16-49-453.png|thumbnail! > Tested in: > Red Hat CodeReady Studio > Version: 12.14.0.GA > Build id: GA-v20200205-0411-B5842 > Build date: 20200205-0411 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-27032) Update Maven ITests to JavaEE 8/7 components

by Jeff MAURY (Jira)

[ https://issues.redhat.com/browse/JBIDE-27032?page=com.atlassian.jira.plug... ] Jeff MAURY updated JBIDE-27032: ------------------------------- Sprint: devex #179 Jan/Feb 2020, devex #180 Feb/Mar 2020 (was: devex #179 Jan/Feb 2020) > Update Maven ITests to JavaEE 8/7 components > -------------------------------------------- > > Key: JBIDE-27032 > URL: https://issues.redhat.com/browse/JBIDE-27032 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, maven > Affects Versions: 4.14.0.AM1 > Reporter: Josef Kopriva > Assignee: Zbyněk Červinka > Priority: Major > Fix For: 4.14.0.Final > > > Please review all maven ITests and update to use JavaEE 8 components. > Use https://access.redhat.com/articles/113373 to find correct versions > You need to go through all tests and review them, if they are using old technology/specification and create new tests to use technology/specification from Java EE7 and 8. > E.g. all configurators tests and maybe more tests. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-27022) Add Java EE example.itests to use Java EE 8 repo

by Jeff MAURY (Jira)

[ https://issues.redhat.com/browse/JBIDE-27022?page=com.atlassian.jira.plug... ] Jeff MAURY updated JBIDE-27022: ------------------------------- Sprint: devex #179 Jan/Feb 2020, devex #180 Feb/Mar 2020 (was: devex #179 Jan/Feb 2020) > Add Java EE example.itests to use Java EE 8 repo > ------------------------------------------------ > > Key: JBIDE-27022 > URL: https://issues.redhat.com/browse/JBIDE-27022 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: project-examples > Affects Versions: 4.14.0.AM1 > Reporter: Zbyněk Červinka > Assignee: Zbyněk Červinka > Priority: Minor > Fix For: 4.14.0.Final > > > Add profile and jobs to use Java EE example.itests to use Java EE 8 repo: https://github.com/javaee-samples/javaee8-samples -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26200) Server adapter wizard: Imported project is not filled into "Eclipse Project"

by Jeff MAURY (Jira)

[ https://issues.redhat.com/browse/JBIDE-26200?page=com.atlassian.jira.plug... ] Jeff MAURY updated JBIDE-26200: ------------------------------- Sprint: devex #179 Jan/Feb 2020, devex #180 Feb/Mar 2020 (was: devex #179 Jan/Feb 2020) > Server adapter wizard: Imported project is not filled into "Eclipse Project" > ---------------------------------------------------------------------------- > > Key: JBIDE-26200 > URL: https://issues.redhat.com/browse/JBIDE-26200 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Final > Reporter: André Dietisheim > Assignee: Josef Kopriva > Priority: Major > Labels: import_wizard, server_adapter_wizard > Fix For: 4.15.x > > Attachments: image-2018-07-16-14-26-26-327.png, screenshot-1.png > > > steps: > # ASSERT: make sure you have a service running on your server but it's *NOT* present in your Eclipse workspace (ex. created via the nodejs-mongo-persistent template) > # EXEC: in Explorer: select the service of your application (ex. nodejs-mongo-persisten service) and pick "Server Adapter..." in it's context menu > # ASSERT: server adapter wizard shows up with "Eclipse Project" empty and marked with an error > !image-2018-07-16-14-26-26-327.png! > # EXEC: hit "Import" to the right of the "Eclipse Project" text field > # ASSERT: "Select Build Config" wizard shows up listing a build config to import (ex. nodejs-mongo-persistent) > # EXEC: select the build config and finish the wizard > # ASSERT: "Select Build Config" wizard disappears, you're back in the "Server Adapter" wizard & the project is imported to your worksapce in the background and eventually shows up in the workspace > Result: > "Eclipse Project" is not filled out (even though I just imported it), text field is therefore still decorated with an error > !screenshot-1.png! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26887) Install containers tools on slaves

by Jeff MAURY (Jira)

[ https://issues.redhat.com/browse/JBIDE-26887?page=com.atlassian.jira.plug... ] Jeff MAURY updated JBIDE-26887: ------------------------------- Sprint: devex #179 Jan/Feb 2020, devex #180 Feb/Mar 2020 (was: devex #179 Jan/Feb 2020) > Install containers tools on slaves > ---------------------------------- > > Key: JBIDE-26887 > URL: https://issues.redhat.com/browse/JBIDE-26887 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Affects Versions: 4.13.0.AM1 > Reporter: Zbyněk Červinka > Assignee: Josef Kopriva > Priority: Major > Fix For: 4.14.0.Final > > > *Info:* > When provisioning scripts are running with labels "jbds docker" to provision RHEL 8+, the script automatically install podman instead docker (see the *label/rhel/docker.sh*). BUT THE SCRIPT IS STILL FAILING - IT NEEDS TO BE INVESTIGATED AND FIXED. > *See the log with assert from Jenkins:* > {code:java} > [branch_rhel8-1-x64-jbds] Writing manifest to image destination > [branch_rhel8-1-x64-jbds] Storing signatures > [branch_rhel8-1-x64-jbds] 7b96db9590a8f5184871203f02f05e0160390edb1facd1bcf199e270815d037c > [branch_rhel8-1-x64-jbds] Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg. > [branch_rhel8-1-x64-jbds] 7b96db9590a8f5184871203f02f05e0160390edb1facd1bcf199e270815d037c > [branch_rhel8-1-x64-jbds] test_talk_to_the_outer_world > [branch_rhel8-1-x64-jbds] Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg. > [branch_rhel8-1-x64-jbds] ASSERT:Unable to ping remote hosts from container: PING 10.38.5.26 (10.38.5.26) 56(84) bytes of data. > [branch_rhel8-1-x64-jbds] > [branch_rhel8-1-x64-jbds] --- 10.38.5.26 ping statistics --- > [branch_rhel8-1-x64-jbds] 1 packets transmitted, 0 received, 100% packet loss, time 0ms > [branch_rhel8-1-x64-jbds] Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg. > [branch_rhel8-1-x64-jbds] c2c03a296d2329a4f3ab72a7bf38b78a8a80108204d326b0139d6af700e152d1 > [branch_rhel8-1-x64-jbds] > [branch_rhel8-1-x64-jbds] Ran 4 tests. > [branch_rhel8-1-x64-jbds] > [branch_rhel8-1-x64-jbds] FAILED (failures=1) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

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 February 2020