March 2020 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-27081) New JSF project with the 2.3 JSF version could not be build (WildFly 18 Runtime is used)

by Zbyněk Červinka (Jira)

[ https://issues.redhat.com/browse/JBIDE-27081?page=com.atlassian.jira.plug... ] Zbyněk Červinka updated JBIDE-27081: ------------------------------------ Steps to Reproduce: 1) create new JSF project with the JSF 2.3 version (WildFly 18 Runtime is used), both Java 8 and Java 11 2) convert to maven (configure -> convert to maven project -> use WAR as packiging -> Finish Finish) 3) try to build the project (mvn clean install) -> you will see the error was: 1) create new JSF project with the JSF 2.3 version (WildFly 18 Runtime is used) 2) convert to maven (configure -> convert to maven project -> use WAR as packiging -> Finish Finish) 3) try to build the project (mvn clean install) -> you will see the error > New JSF project with the 2.3 JSF version could not be build (WildFly 18 Runtime is used) > ---------------------------------------------------------------------------------------- > > Key: JBIDE-27081 > URL: https://issues.redhat.com/browse/JBIDE-27081 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.14.0.Final > Reporter: Zbyněk Červinka > Assignee: Jeff MAURY > Priority: Major > > {code:java} > ERROR] Failed to execute goal on project project123: Could not resolve dependencies for project project123:project123:war:0.0.1-SNAPSHOT: The following artifacts could not be resolved: org.apache.taglibs:taglibs-standard-compat:jar:1.2.6-RC1, org.apache.taglibs:taglibs-standard-spec:jar:1.2.6-RC1, org.apache.taglibs:taglibs-standard-impl:jar:1.2.6-RC1, org.infinispan:infinispan-core:jar:4.2.1.FINAL: Failure to find org.apache.taglibs:taglibs-standard-compat:jar:1.2.6-RC1 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced -> [Help 1] > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27081) New JSF project with the 2.3 JSF version could not be build (WildFly 18 Runtime is used)

by Zbyněk Červinka (Jira)

[ https://issues.redhat.com/browse/JBIDE-27081?page=com.atlassian.jira.plug... ] Zbyněk Červinka updated JBIDE-27081: ------------------------------------ Description: {code:java} ERROR] Failed to execute goal on project project123: Could not resolve dependencies for project project123:project123:war:0.0.1-SNAPSHOT: The following artifacts could not be resolved: org.apache.taglibs:taglibs-standard-compat:jar:1.2.6-RC1, org.apache.taglibs:taglibs-standard-spec:jar:1.2.6-RC1, org.apache.taglibs:taglibs-standard-impl:jar:1.2.6-RC1, org.infinispan:infinispan-core:jar:4.2.1.FINAL: Failure to find org.apache.taglibs:taglibs-standard-compat:jar:1.2.6-RC1 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced -> [Help 1] {code} > New JSF project with the 2.3 JSF version could not be build (WildFly 18 Runtime is used) > ---------------------------------------------------------------------------------------- > > Key: JBIDE-27081 > URL: https://issues.redhat.com/browse/JBIDE-27081 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.14.0.Final > Reporter: Zbyněk Červinka > Assignee: Jeff MAURY > Priority: Major > > {code:java} > ERROR] Failed to execute goal on project project123: Could not resolve dependencies for project project123:project123:war:0.0.1-SNAPSHOT: The following artifacts could not be resolved: org.apache.taglibs:taglibs-standard-compat:jar:1.2.6-RC1, org.apache.taglibs:taglibs-standard-spec:jar:1.2.6-RC1, org.apache.taglibs:taglibs-standard-impl:jar:1.2.6-RC1, org.infinispan:infinispan-core:jar:4.2.1.FINAL: Failure to find org.apache.taglibs:taglibs-standard-compat:jar:1.2.6-RC1 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced -> [Help 1] > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27081) New JSF project with the 2.3 JSF version could not be build (WildFly 18 Runtime is used)

by Zbyněk Červinka (Jira)

Zbyněk Červinka created JBIDE-27081: --------------------------------------- Summary: New JSF project with the 2.3 JSF version could not be build (WildFly 18 Runtime is used) Key: JBIDE-27081 URL: https://issues.redhat.com/browse/JBIDE-27081 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Zbyněk Červinka Assignee: Jeff MAURY -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27057) rootProject.name in Gradle Project is incorrect

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-27057?page=com.atlassian.jira.plug... ] Josef Kopriva reassigned JBIDE-27057: ------------------------------------- Assignee: Jeff MAURY > rootProject.name in Gradle Project is incorrect > ----------------------------------------------- > > Key: JBIDE-27057 > URL: https://issues.redhat.com/browse/JBIDE-27057 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: quarkus > Affects Versions: 4.14.0.Final > Reporter: Oleksii Korniienko > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.15.0.AM1 > > > rootProject.name in settings.gradle in Gradle Project is "code-with-quarkus" not name of project > Red Hat CodeReady Studio > Version: 12.14.0.GA > Build id: GA-v20200213-1019-B5905 > Build date: 20200213-1019 > Java > openjdk version "1.8.0_232" > OpenJDK Runtime Environment (build 1.8.0_232-b09) > OpenJDK 64-Bit Server VM (build 25.232-b09, mixed mode) > OS > RHEL 8.0 > 64-bit > GNOME > Version: 3.28.2 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27062) no Quarkus Extension are added to Gradle project

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-27062?page=com.atlassian.jira.plug... ] Josef Kopriva reassigned JBIDE-27062: ------------------------------------- Assignee: Jeff MAURY > no Quarkus Extension are added to Gradle project > ------------------------------------------------ > > Key: JBIDE-27062 > URL: https://issues.redhat.com/browse/JBIDE-27062 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: quarkus > Affects Versions: 4.14.0.Final > Reporter: Oleksii Korniienko > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.15.0.AM1 > > Attachments: Screenshot from 2020-02-19 12-47-05.png > > > Can`t add any quarkus extensions to Gradle project. > Red Hat CodeReady Studio > Version: 12.14.0.GA > Build id: GA-v20200213-1019-B5905 > Build date: 20200213-1019 > Java > openjdk version "1.8.0_232" > OpenJDK Runtime Environment (build 1.8.0_232-b09) > OpenJDK 64-Bit Server VM (build 25.232-b09, mixed mode) > OS > RHEL 8.0 > 64-bit > GNOME > Version: 3.28.2 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27059) Server adapter: hot-deployment of SpringBoot app upon code changes for SpringBoot is broken

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-27059?page=com.atlassian.jira.plug... ] Josef Kopriva commented on JBIDE-27059: --------------------------------------- Hi [~adietish], I have tried it and it works on OpenShift 3, but it did not work for me on OpenShift 4.3.0, I will try to investigate it further. > Server adapter: hot-deployment of SpringBoot app upon code changes for SpringBoot is broken > ------------------------------------------------------------------------------------------- > > Key: JBIDE-27059 > URL: https://issues.redhat.com/browse/JBIDE-27059 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.14.0.AM1 > Reporter: Josef Kopriva > Assignee: André Dietisheim > Priority: Major > Labels: openshift_v3, server_adapter > Fix For: 4.15.0.AM1 > > > Important: the demo project used for this fuse-on-openshift only works with *Java 8* (wont with java 11). > I am using this class for testing: all source is there: > https://github.com/jbosstools/jbosstools-openshift/blob/master/itests/org... > Everything works as expected, until I change the code, afterwards code is synching to pod, but the the log for pod is not changing accordingly to code changes. > Project: > https://github.com/jbosstools/jbosstools-openshift/blob/master/itests/org... > mvn parameters: > -Dkubernetes.master=https://api.openshift4-crs.crs.codereadyqe.com:6443/ > -Dkubernetes.namespace=fuse-on-openshift > -Dkubernetes.auth.basic.username=xxx > -Dkubernetes.auth.basic.password=xxx > -Dfabric8.mode=openshift > -Dkubernetes.trust.certificates=true > -Dfabric8.build.strategy=s2i > -Dkubernetes.auth.tryServiceAccount=false > -Dfabric8.generator.from=fabric8/s2i-java > -Dfabric8.generator.fromMode=docker > -Dkubernetes.auth.tryKubeConfig=false > Tested in: > Red Hat CodeReady Studio > Version: 12.14.0.AM1 > Build id: AM1-v20200123-0055-B5802 > Build date: 20200123-0055 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26899) Refreshing non-functional connection to CRC doesnt help (need to create new)

by Ondrej Dockal (Jira)

[ https://issues.redhat.com/browse/JBIDE-26899?page=com.atlassian.jira.plug... ] Ondrej Dockal closed JBIDE-26899. --------------------------------- Cannot reproduce now, closing. > Refreshing non-functional connection to CRC doesnt help (need to create new) > ---------------------------------------------------------------------------- > > Key: JBIDE-26899 > URL: https://issues.redhat.com/browse/JBIDE-26899 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift > Affects Versions: 4.13.0.Final > Environment: CRC > Reporter: André Dietisheim > Assignee: André Dietisheim > Priority: Major > Fix For: 4.14.0.AM1 > > > *Steps* - not reproducibe at 100%, happens from time to time: > # ASSERT: have ~/.crc folder killed > # EXEC: create new CRC server adapter & Start it > # ASSERT: OpenShift connection is created > # ASSERT: Connection fails to authorize, reports that it cannot access resources using system:anonymous. > # EXEC: try to login with *oc login*. If oc reports *Error from server (InternalError): Internal error occurred: unexpected response: 400*, repeat until it succeeds (waiting required) > # EXEC: Once oc login succeeds: refresh the connection in Eclipse > Result: > Connecting still fails with the same error. > Expected result: > Refreshing the connection should succeed once the server is fully up and running and oc succeeds to log in. > Workaround: > # EXEC: edit the connection instead of refreshing it (ex. remove a character from username and add it back again) > Result: > Connecting succeeds -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26869) CRC server adapter: OpenShift connection that is created is unusable at times

by Ondrej Dockal (Jira)

[ https://issues.redhat.com/browse/JBIDE-26869?page=com.atlassian.jira.plug... ] Ondrej Dockal closed JBIDE-26869. --------------------------------- Cannot reproduce now, closing. > CRC server adapter: OpenShift connection that is created is unusable at times > ----------------------------------------------------------------------------- > > Key: JBIDE-26869 > URL: https://issues.redhat.com/browse/JBIDE-26869 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift > Affects Versions: 4.13.0.AM1 > Environment: CRC Beta5 > Reporter: André Dietisheim > Assignee: André Dietisheim > Priority: Critical > Fix For: 4.14.0.AM1 > > Attachments: crc-connection-error.mp4, start-crc-error-openshift-conn.mp4 > > > *Steps* - not reproducibe at 100%, happens from time to time: > # ASSERT: have ~/.crc folder killed > # EXEC: create new CRC server adapter & Start it > # ASSERT: OpenShift connection is created > *Result:* > Connection fails to authorize, reports that it cannot access resources using system:anonymous. Refreshing the connection doesn't help, so it's apparently not a timing issue (ex. creating the connection before the cluster is fully up and running) > {code} > com.openshift.restclient.authorization.ResourceForbiddenException: forbidden: User "system:anonymous" cannot get path "/oauth/authorize" forbidden: User "system:anonymous" cannot get path "/oauth/authorize" > at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.createOpenShiftException(ResponseCodeInterceptor.java:111) > at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:66) > at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:112) > at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:87) > at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.kt:184) > at okhttp3.RealCall.execute(RealCall.kt:66) > at com.openshift.internal.restclient.okhttp.OpenShiftAuthenticator.tryAuth(OpenShiftAuthenticator.java:109) > at com.openshift.internal.restclient.okhttp.OpenShiftAuthenticator.authenticate(OpenShiftAuthenticator.java:62) > at okhttp3.internal.http.RetryAndFollowUpInterceptor.followUpRequest(RetryAndFollowUpInterceptor.kt:213) > at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.kt:102) > at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:112) > at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:87) > at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:55) > at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:112) > at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:87) > at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.kt:184) > at okhttp3.RealCall.execute(RealCall.kt:66) > at com.openshift.internal.restclient.DefaultClient.request(DefaultClient.java:315) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:307) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:275) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:243) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:226) > at com.openshift.internal.restclient.DefaultClient.get(DefaultClient.java:423) > at com.openshift.internal.restclient.authorization.AuthorizationContext.isAuthorized(AuthorizationContext.java:63) > at org.jboss.tools.openshift.core.connection.Connection.authorize(Connection.java:237) > at org.jboss.tools.openshift.core.connection.Connection.connect(Connection.java:226) > at org.jboss.tools.openshift.internal.crc.server.core.listeners.ConfigureCRCFrameworksListener.configureOpenshift(ConfigureCRCFrameworksListener.java:102) > at org.jboss.tools.openshift.internal.crc.server.core.listeners.ConfigureCRCFrameworksListener.configureFrameworks(ConfigureCRCFrameworksListener.java:73) > at org.jboss.tools.openshift.internal.crc.server.core.listeners.ConfigureCRCFrameworksListener$1.run(ConfigureCRCFrameworksListener.java:66) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26972) Update 4.14.0.AM1 Target Platform (Docker tooling, ...) for 2019-12.GA

by Ondrej Dockal (Jira)

[ https://issues.redhat.com/browse/JBIDE-26972?page=com.atlassian.jira.plug... ] Ondrej Dockal closed JBIDE-26972. --------------------------------- > Update 4.14.0.AM1 Target Platform (Docker tooling, ...) for 2019-12.GA > ---------------------------------------------------------------------- > > Key: JBIDE-26972 > URL: https://issues.redhat.com/browse/JBIDE-26972 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.14.0.AM1 > Reporter: Jeff MAURY > Assignee: Stephane Bouchet > Priority: Major > Fix For: 4.14.0.AM1 > > Attachments: p2diff_log_jbosstools_2020-01-15_12-02.txt > > > Include also Eclipse Wild Web Developer as we may migrate the OpenShift JS debug from JSDT to Eclipse Wild Web Developer -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26912) Remove Code Recommenders from the TP

by Ondrej Dockal (Jira)

[ https://issues.redhat.com/browse/JBIDE-26912?page=com.atlassian.jira.plug... ] Ondrej Dockal closed JBIDE-26912. --------------------------------- > Remove Code Recommenders from the TP > ------------------------------------ > > Key: JBIDE-26912 > URL: https://issues.redhat.com/browse/JBIDE-26912 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.13.0.Final > Reporter: Jeff MAURY > Assignee: Stephane Bouchet > Priority: Major > Fix For: 4.14.0.AM1 > > > Eclipse Recommenders has been removed from upstream EPPs starting 2018-12. > We should remove it from TP and Studio because it's not maintained anymore and causes issues on Java11 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 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 March 2020