December 2019 - jbosstools-issues

[JBoss JIRA] (JBIDE-26987) Deprecate vpe/forge/jst components

by Jeff MAURY (Jira)

[ https://issues.redhat.com/browse/JBIDE-26987?page=com.atlassian.jira.plug... ] Jeff MAURY commented on JBIDE-26987: ------------------------------------ What needs to be clarified is if this requires some changes in Central. The only other places are in website and QE > Deprecate vpe/forge/jst components > ---------------------------------- > > Key: JBIDE-26987 > URL: https://issues.redhat.com/browse/JBIDE-26987 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central, forge, jst, visual-page-editor-core > Affects Versions: 4.13.0.Final > Reporter: Stephane Bouchet > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.14.0.Final > > > Mark following components as not fully tested anymore : > - VPE > - Forge > - JST > The task is to communicate theses components are not yet removed from JBossTools/Studio, but are not anymore fully tested. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26987) Deprecate vpe/forge/jst components

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-26987?page=com.atlassian.jira.plug... ] Stephane Bouchet reassigned JBIDE-26987: ---------------------------------------- Assignee: Stephane Bouchet > Deprecate vpe/forge/jst components > ---------------------------------- > > Key: JBIDE-26987 > URL: https://issues.redhat.com/browse/JBIDE-26987 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central, forge, jst, visual-page-editor-core > Affects Versions: 4.14.x > Reporter: Stephane Bouchet > Assignee: Stephane Bouchet > Priority: Major > Fix For: 4.14.x > > > Mark following components as not fully tested anymore : > - VPE > - Forge > - JST > The task is to communicate theses components are not yet removed from JBossTools/Studio, but are not anymore fully tested. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26987) Deprecate vpe/forge/jst components

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-26987?page=com.atlassian.jira.plug... ] Stephane Bouchet reassigned JBIDE-26987: ---------------------------------------- Assignee: Jeff MAURY (was: Stephane Bouchet) > Deprecate vpe/forge/jst components > ---------------------------------- > > Key: JBIDE-26987 > URL: https://issues.redhat.com/browse/JBIDE-26987 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central, forge, jst, visual-page-editor-core > Affects Versions: 4.14.x > Reporter: Stephane Bouchet > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.14.x > > > Mark following components as not fully tested anymore : > - VPE > - Forge > - JST > The task is to communicate theses components are not yet removed from JBossTools/Studio, but are not anymore fully tested. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26987) Deprecate vpe/forge/jst components

by Stephane Bouchet (Jira)

Stephane Bouchet created JBIDE-26987: ---------------------------------------- Summary: Deprecate vpe/forge/jst components Key: JBIDE-26987 URL: https://issues.redhat.com/browse/JBIDE-26987 Project: Tools (JBoss Tools) Issue Type: Task Components: central, forge, jst, visual-page-editor-core Affects Versions: 4.14.x Reporter: Stephane Bouchet Fix For: 4.14.x Mark following components as not fully tested anymore : - VPE - Forge - JST The task is to communicate theses components are not yet removed from JBossTools/Studio, but are not anymore fully tested. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26913) cdi.itests for CDI 1.0 and 1.1 contains tests for trim and several failing tests (Asserts, NPEs ...)

by Zbyněk Červinka (Jira)

[ https://issues.redhat.com/browse/JBIDE-26913?page=com.atlassian.jira.plug... ] Zbyněk Červinka updated JBIDE-26913: ------------------------------------ Summary: cdi.itests for CDI 1.0 and 1.1 contains tests for trim and several failing tests (Asserts, NPEs ...) (was: cdi.itests for CDI 1.0 and 1.1 contains tests for trim and several failing tests (Asserts and NPEs)) > cdi.itests for CDI 1.0 and 1.1 contains tests for trim and several failing tests (Asserts, NPEs ...) > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-26913 > URL: https://issues.redhat.com/browse/JBIDE-26913 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests > Affects Versions: 4.13.0.AM1 > Environment: all OSes > Reporter: Zbyněk Červinka > Assignee: Zbyněk Červinka > Priority: Major > Fix For: 4.14.0.AM1 > > > There are several issues in the CDI 1.0 and the CDI 1.1 itests, several actions needs to be performed: > - remove the TRIM tests from the CDI 1.0 and the CDI 1.1 itests > - fix the failing 'testExcludedBeans' WeldExcludeTestCDI10 and WeldExcludeTestCDI11 tests (CDI 1.0 and CDI 1.1) > - fix the failing 'testVetoedAnnotation' VetoedAnnotationTestCDI11 test (CDI 1.1) > - fix the failing 'testParametersAnnotationvalidation' BeanParametersAnnotationTestCDI11 test (CDI 1.1) > - fix the failing 'testExcludedBeans' ExcludeBeanTestCDI11 test (CDI 1.1) > - fix the failing 'testModeAnnotated' and 'testWithoutBeansXml' BeansXMLDiscoveryModesTestCDI11 tests (CDI 1.1) > - fix the failing 'testValidationOfBeanDiscoveryInExplicitArchives' BeanDiscoveryInExplicitArchivesTestCDI11 test (CDI 1.1) > - fix the failing 'testValidationOfBeanDiscoveryInImplicitArchives' BeanDiscoveryInImplicitArchivesTestCDI11 test (CDI 1.1) > - fix the failing 'testBuildInContextsWarnings' WeldBuiltInContextsTestCDI11 test (CDI 1.1) -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26781) Migrate Project Examples integration tests into job DSL

by Zbyněk Červinka (Jira)

[ https://issues.redhat.com/browse/JBIDE-26781?page=com.atlassian.jira.plug... ] Zbyněk Červinka resolved JBIDE-26781. ------------------------------------- Resolution: Done > Migrate Project Examples integration tests into job DSL > ------------------------------------------------------- > > Key: JBIDE-26781 > URL: https://issues.redhat.com/browse/JBIDE-26781 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: integration-tests, qa > Affects Versions: 4.14.0.AM1 > Reporter: Ondrej Dockal > Assignee: Zbyněk Červinka > Priority: Critical > Fix For: 4.14.0.AM1 > > > Rewrite QE integration tests into job DSL and place them under dev-platform/cci-config repo -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26781) Migrate Project Examples integration tests into job DSL

by Zbyněk Červinka (Jira)

[ https://issues.redhat.com/browse/JBIDE-26781?page=com.atlassian.jira.plug... ] Zbyněk Červinka closed JBIDE-26781. ----------------------------------- Merge request has been merged, I am closing this JIRA. > Migrate Project Examples integration tests into job DSL > ------------------------------------------------------- > > Key: JBIDE-26781 > URL: https://issues.redhat.com/browse/JBIDE-26781 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: integration-tests, qa > Affects Versions: 4.14.0.AM1 > Reporter: Ondrej Dockal > Assignee: Zbyněk Červinka > Priority: Critical > Fix For: 4.14.0.AM1 > > > Rewrite QE integration tests into job DSL and place them under dev-platform/cci-config repo -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26986) Quarkus launch configuration is broken

by Jeff MAURY (Jira)

[ https://issues.redhat.com/browse/JBIDE-26986?page=com.atlassian.jira.plug... ] Jeff MAURY updated JBIDE-26986: ------------------------------- Story Points: 5 > Quarkus launch configuration is broken > -------------------------------------- > > Key: JBIDE-26986 > URL: https://issues.redhat.com/browse/JBIDE-26986 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: quarkus > Affects Versions: 4.14.0.AM1 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.14.0.AM1 > > > When you try to launch a Quarkus configuration; you have the following error message: > {code:java} > Error : unable to find or load the main class io.quarkus.dev.DevModeMain > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26891) Connection wizard: "Override oc version" complains even though nothing to complain about

by Jeff MAURY (Jira)

[ https://issues.redhat.com/browse/JBIDE-26891?page=com.atlassian.jira.plug... ] Jeff MAURY updated JBIDE-26891: ------------------------------- Sprint: devex #174 Oct 2019, devex #175 Nov 2019, devex #176 Nov/Dec 2019 (was: devex #174 Oct 2019, devex #175 Nov 2019, devex #176 Nov/Dec 2019, devex #177 Dec 2019) > Connection wizard: "Override oc version" complains even though nothing to complain about > ---------------------------------------------------------------------------------------- > > Key: JBIDE-26891 > URL: https://issues.redhat.com/browse/JBIDE-26891 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.13.0.AM1 > Reporter: André Dietisheim > Assignee: André Dietisheim > Priority: Major > Labels: connection_wizard > Fix For: 4.14.x > > Attachments: image-2019-10-14-22-57-02-582.png > > > Steps: > # ASSERT: make sure that you have a valid *oc* binary set in your preferences (Preferences > OpenShift > 'oc' executable location > # EXEC: launch connection wizard (New > Other > OpenShift) > # EXEC: hit "Advanced >>" & check "Override 'oc' location:" > Result: > The input field for "Override 'oc' location:" is decorated with a warning even though the path that is used (that is taken from necessarily valid preferences) is perfectly valid > !image-2019-10-14-22-57-02-582.png! -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

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

by Jeff MAURY (Jira)

[ https://issues.redhat.com/browse/JBIDE-26869?page=com.atlassian.jira.plug... ] Jeff MAURY updated JBIDE-26869: ------------------------------- Sprint: devex #173 Oct 2019, devex #175 Nov 2019, devex #176 Nov/Dec 2019 (was: devex #173 Oct 2019, devex #175 Nov 2019, devex #176 Nov/Dec 2019, devex #177 Dec 2019) > 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: 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)

5 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2019