June 2020 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26916) Dynamic Web Project shows errors after converting to maven project when using WildFly 18 as target runtime and Java 11

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-26916?page=com.atlassian.jira.plug... ] Stephane Bouchet updated JBIDE-26916: ------------------------------------- Fix Version/s: 4.16.0.Final (was: 4.16.0.AM1) > Dynamic Web Project shows errors after converting to maven project when using WildFly 18 as target runtime and Java 11 > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26916 > URL: https://issues.redhat.com/browse/JBIDE-26916 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.13.0.AM1 > Environment: All OSes > Reporter: Zbyněk Červinka > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.16.0.Final > > Attachments: RHCRS_preferences.png, dynamic_web_project_after_converting_to_maven.png, new_server_settings.png, project_facets_when_creating_the_project.png > > > h2. Basic information on this issue: > - Issue appears only when using WildFly 18 as target runtime and Java 11 (see the 'Steps to reproduce' section and printscreens in the attachment) > - Issue does not appear on WildFly 16 and on WildFly 17 (tested on both Java 8 and 11; this issue has not appeared even if I have mixed Java version settings in workspace/server runtime JRE/Project fFacets, no issue for any combination) > h2. Error messages from the Problems view: > * Missing artifact jakarta.jws:jakarta.jws-api:jar:2.1.0 pom.xml > * The container 'Maven Dependencies' references non existing library '/Users/zcervink/.m2/repository/jakarta/jws/jakarta.jws-api/2.1.0/jakarta.jws-api-2.1.0.jar' > * The project cannot be built until build path errors are resolved > h2. Tested solution - insert the following dependency into the pom.xml and all the problems in the Problems view disappear > {code:java} > <dependency> > <groupId>jakarta.jws</groupId> > <artifactId>jakarta.jws-api</artifactId> > <version>1.1.1</version> > </dependency> > {code} > h2. Red Hat CodeReady Studio version (version used to testing when creating this JIRA): > Version: 12.13.0.GA > Build id: GA-v20191024-0752-B5215 > Build date: 20191024-0752 > h2. Red Hat CodeReady Studio (newest version used to testing when updating this JIRA): > Version: 12.14.0.AM1 > Build id: AM1-v20191122-0713-B5330 > Build date: 20191122-0713 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26888) Replace http access to https

by Stephane Bouchet (Jira)

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

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26858) Implement missing CDK unit tests

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-26858?page=com.atlassian.jira.plug... ] Stephane Bouchet updated JBIDE-26858: ------------------------------------- Fix Version/s: 4.16.0.Final (was: 4.16.0.AM1) > Implement missing CDK unit tests > -------------------------------- > > Key: JBIDE-26858 > URL: https://issues.redhat.com/browse/JBIDE-26858 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk > Affects Versions: 4.13.0.AM1 > Reporter: Ondrej Dockal > Priority: Major > Fix For: 4.16.0.Final > > > There are missing unit test that require our attention. Ie. CDKServerWizardFragment. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26856) Download Runtimes: License is not displayed, retrieval errors

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-26856?page=com.atlassian.jira.plug... ] Stephane Bouchet updated JBIDE-26856: ------------------------------------- Fix Version/s: 4.16.0.Final (was: 4.16.0.AM1) > Download Runtimes: License is not displayed, retrieval errors > ------------------------------------------------------------- > > Key: JBIDE-26856 > URL: https://issues.redhat.com/browse/JBIDE-26856 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.13.0.AM1 > Reporter: André Dietisheim > Priority: Major > Labels: runtime_detection > Fix For: 4.16.0.Final > > Attachments: lincense-retrieval-error.png, screenshot-1.png > > > Steps: > # EXEC: Preferences > JBoss Tools > JBoss Runtime Detection, hit button "Download" (or access it via new server wizard) > # ASSERT: downloadable servers are listed > # EXEC: select "CDK v3.9.0" & hit "Next" > # EXEC: provide/confirm credentials & hit "Next" > Result: > License is not displayed, an error dialog pops up instead. I'd argue that the license cannot be correctly consented to if it's not displayed. > !lincense-retrieval-error.png! -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26847) An internal error occurred during: "Identify jrt-fs.jar".

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-26847?page=com.atlassian.jira.plug... ] Stephane Bouchet updated JBIDE-26847: ------------------------------------- Fix Version/s: 4.16.0.Final (was: 4.16.0.AM1) > An internal error occurred during: "Identify jrt-fs.jar". > --------------------------------------------------------- > > Key: JBIDE-26847 > URL: https://issues.redhat.com/browse/JBIDE-26847 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.11.0.Final, 4.16.x, 4.12.0.Final > Reporter: Martijn Dashorst > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.16.0.Final > > > I've installed > JBoss Maven Integration 1.9.3.v20190827-1345 org.jboss.tools.maven.feature.feature.group Red Hat > And when I open anything from the Java class library I get a popup with the message: > *An internal error occurred during: "Identify jrt-fs.jar".* > I don't have the full class library of the java runtime committed to my memory, so I have to look at the source quite often and this popup is getting literally in the way. > {code:java} > java.lang.NoClassDefFoundError: javax/xml/bind/JAXBContext > at org.jboss.tools.maven.core.internal.identification.NexusRepositoryIdentifier.searchArtifactFromRemoteNexusRepository(NexusRepositoryIdentifier.java:96) > at org.jboss.tools.maven.core.internal.identification.NexusRepositoryIdentifier.getArtifactFromRemoteNexusRepository(NexusRepositoryIdentifier.java:78) > at org.jboss.tools.maven.core.internal.identification.NexusRepositoryIdentifier.identify(NexusRepositoryIdentifier.java:50) > at org.jboss.tools.maven.core.internal.identification.FileIdentificationManager.identify(FileIdentificationManager.java:91) > at org.jboss.tools.maven.sourcelookup.ui.actions.AttachSourcesActionDelegate$1.run(AttachSourcesActionDelegate.java:114) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63) > Caused by: java.lang.ClassNotFoundException: javax.xml.bind.JAXBContext cannot be found by org.jboss.tools.maven.core_1.9.3.v20190827-1345 > at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:514) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:425) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:155) > at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) > ... 6 more > {code} > It was reported in https://issues.jboss.org/browse/JBIDE-26571, apparently not fixed in https://issues.jboss.org/browse/JBIDE-26500 as the latest SNAPSHOT plugins still exhibit this error (in 2019.9) > This is the set of JBoss Tools Maven plugins I have installed: > JBoss Maven Integration 1.9.3.v20190827-1345 org.jboss.tools.maven.feature.feature.group Red Hat > m2e - Maven Integration for Eclipse (includes Incubating components) 1.13.0.20190716-1624 org.eclipse.m2e.feature.feature.group Eclipse.org - m2e > m2e-wtp - Maven Integration for WTP 1.4.2.20190530-0057 org.eclipse.m2e.wtp.feature.feature.group Eclipse.org - m2e-wtp > Maven SCM Handler for EGit 0.15.1.201806191431 org.sonatype.m2e.egit.feature.feature.group Sonatype, Inc. > JBoss Tools Maven Packaging Configurator 1.9.3.v20190827-1345 org.jboss.tools.maven.jbosspackaging.feature.feature.group Red Hat > JBoss Tools Maven Source Lookup 1.9.3.v20190827-1345 org.jboss.tools.maven.sourcelookup.feature.feature.group Red Hat -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27125) OpenShift: Create Service` command should ask input for required and optionally not required service template properties

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-27125?page=com.atlassian.jira.plug... ] Stephane Bouchet updated JBIDE-27125: ------------------------------------- Fix Version/s: 4.16.0.Final (was: 4.16.0.AM1) > OpenShift: Create Service` command should ask input for required and optionally not required service template properties > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-27125 > URL: https://issues.redhat.com/browse/JBIDE-27125 > 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.16.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27119) Hover over Microprofile config property annotation does not work

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-27119?page=com.atlassian.jira.plug... ] Stephane Bouchet updated JBIDE-27119: ------------------------------------- Fix Version/s: 4.16.0.Final (was: 4.16.0.AM1) > Hover over Microprofile config property annotation does not work > ---------------------------------------------------------------- > > Key: JBIDE-27119 > URL: https://issues.redhat.com/browse/JBIDE-27119 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: quarkus > Affects Versions: 4.14.0.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.16.0.Final > > > When hovering over a Microprofile ConfigProperty name attribute, an LSP Hover request should be sent to that the current value of the property should be displayed. It is not, probably because the LSP Hover mecanism is not invoked against the JDT source editor. > To be checked with [~mickael_istria] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

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

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-27085?page=com.atlassian.jira.plug... ] Stephane Bouchet updated JBIDE-27085: ------------------------------------- Fix Version/s: 4.16.0.Final (was: 4.16.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 > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.16.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)

5 years, 9 months

1
0
0 / 0

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

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-27084?page=com.atlassian.jira.plug... ] Stephane Bouchet updated JBIDE-27084: ------------------------------------- Fix Version/s: 4.16.0.Final (was: 4.16.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.16.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)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27068) oc binary 4.3.0 were not recognized

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-27068?page=com.atlassian.jira.plug... ] Stephane Bouchet updated JBIDE-27068: ------------------------------------- Fix Version/s: 4.16.0.Final (was: 4.16.0.AM1) > oc binary 4.3.0 were not recognized > ----------------------------------- > > Key: JBIDE-27068 > URL: https://issues.redhat.com/browse/JBIDE-27068 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.14.0.Final > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.16.0.Final > > Attachments: JBIDE-27068.bmpr, image-2020-02-21-07-56-00-936.png > > > I have tried OC client for 4.3.0 GA openshift and in CRS is not recognized: > !image-2020-02-21-07-56-00-936.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 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 June 2020