January 2020 - jbosstools-issues - Jboss List Archives

[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 closed JBIDE-26913. ----------------------------------- > 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: cdi > 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 > > > h2. 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)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26750) Update CDI.itests to run on java 11 and add some parameters to the pom.xml

by Zbyněk Červinka (Jira)

[ https://issues.redhat.com/browse/JBIDE-26750?page=com.atlassian.jira.plug... ] Zbyněk Červinka closed JBIDE-26750. ----------------------------------- > Update CDI.itests to run on java 11 and add some parameters to the pom.xml > -------------------------------------------------------------------------- > > Key: JBIDE-26750 > URL: https://issues.redhat.com/browse/JBIDE-26750 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: cdi > Affects Versions: 4.13.0.AM1 > Reporter: Zbyněk Červinka > Assignee: Zbyněk Červinka > Priority: Major > Fix For: 4.14.0.AM1 > > > h2. Perform the following tasks: > - update tests to run on java 11 > - make some refactoring - extract what repeats over and over > - add missing constructors > - make necessary changes to pom.xml and requirements.json files > - update Wildfly to version 18 > - fix failing tests -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26991) Update cdi.itests class and method names to contain the "CDI12" string instead of containing the "CDI11" string

by Zbyněk Červinka (Jira)

[ https://issues.redhat.com/browse/JBIDE-26991?page=com.atlassian.jira.plug... ] Zbyněk Červinka closed JBIDE-26991. ----------------------------------- > Update cdi.itests class and method names to contain the "CDI12" string instead of containing the "CDI11" string > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26991 > URL: https://issues.redhat.com/browse/JBIDE-26991 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: cdi > Affects Versions: 4.14.0.AM1 > Reporter: Zbyněk Červinka > Assignee: Zbyněk Červinka > Priority: Minor > Fix For: 4.14.0.AM1 > > > h2. CDI version in cdi.itests has been updated from version 1.1 to version 1.2; Perform all necessary refactoring to keep the code clean: > * classes and methods in cdi.itests still contains the "CDI11" string in its names, the names must be renamed to contain the "CDI12" string instead > * perform all other necessary changes to complete the update from CDI version 1.1 to CDI version 1.2 (changes in pom.xml, changes in Jenkins settings) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26997) Enable deploy on server by default in example itests

by Zbyněk Červinka (Jira)

[ https://issues.redhat.com/browse/JBIDE-26997?page=com.atlassian.jira.plug... ] Zbyněk Červinka updated JBIDE-26997: ------------------------------------ Description: Set deploy on server on true as default in examples itests (in EAP, WildFly and Java EE integration tests). > Enable deploy on server by default in example itests > ---------------------------------------------------- > > Key: JBIDE-26997 > URL: https://issues.redhat.com/browse/JBIDE-26997 > 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.AM1 > > > Set deploy on server on true as default in examples itests (in EAP, WildFly and Java EE integration tests). -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26997) Enable deploy on server by default in all example itests (EAP, WildFly and Java EE itests)

by Zbyněk Červinka (Jira)

[ https://issues.redhat.com/browse/JBIDE-26997?page=com.atlassian.jira.plug... ] Zbyněk Červinka updated JBIDE-26997: ------------------------------------ Summary: Enable deploy on server by default in all example itests (EAP, WildFly and Java EE itests) (was: Enable deploy on server by default in example itests) > Enable deploy on server by default in all example itests (EAP, WildFly and Java EE itests) > ------------------------------------------------------------------------------------------ > > Key: JBIDE-26997 > URL: https://issues.redhat.com/browse/JBIDE-26997 > 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.AM1 > > > Set deploy on server on true as default in examples itests (in EAP, WildFly and Java EE integration tests). -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26997) Enable deploy on server by default in example itests

by Zbyněk Červinka (Jira)

Zbyněk Červinka created JBIDE-26997: --------------------------------------- Summary: Enable deploy on server by default in example itests Key: JBIDE-26997 URL: https://issues.redhat.com/browse/JBIDE-26997 Project: Tools (JBoss Tools) Issue Type: Task Components: project-examples Affects Versions: 4.14.0.AM1 Reporter: Zbyněk Červinka Assignee: Zbyněk Červinka Fix For: 4.14.0.AM1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26893) Create universal template and label that would accommodate different rhel needed by interop testing team

by Ondrej Dockal (Jira)

[ https://issues.redhat.com/browse/JBIDE-26893?page=com.atlassian.jira.plug... ] Ondrej Dockal updated JBIDE-26893: ---------------------------------- Git Pull Request: (was: https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/cci-config/merge_re...) > Create universal template and label that would accommodate different rhel needed by interop testing team > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26893 > URL: https://issues.redhat.com/browse/JBIDE-26893 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: integration-tests, qa > Affects Versions: 4.13.0.Final > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Major > Labels: jenkins > Fix For: 4.14.0.AM1 > > > We would like to use universal label that would cover different rhel versions that are required by interop testing. The idea is that we will keep one/two label for interop testing slave: rhel-interop (and possibly for both stream, so rhel7-interop and rhel8-interop), which would have used image: rhel-interop-7(8)-snapshot that would have actually needed rhel version to test. During provisioning we will replace snapshot with proper rhel. This way we can keep these two labels and do not need to change interop test job label all the time via PR in cci-config repo. > Reqs: > * UMB trigger for interop rhel to run provision job with > * job will be parametrized based on rhel version given by umb message > * jenkins provisioning job build description needs to be updated to have available info about rhel version > > Pros: > * do not need to change code via PR every time there is new bits to test > * probably can be fully automated > Cons: > * only one version to test at a time > * complex and possibly unstable? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26996) Prepare image RHEL 7.8 Snapshot3 and RHEL 8.2 for testing

by Josef Kopriva (Jira)

Josef Kopriva created JBIDE-26996: ------------------------------------- Summary: Prepare image RHEL 7.8 Snapshot3 and RHEL 8.2 for testing Key: JBIDE-26996 URL: https://issues.redhat.com/browse/JBIDE-26996 Project: Tools (JBoss Tools) Issue Type: Task Components: integration-tests Affects Versions: 4.14.0.AM1 Reporter: Josef Kopriva Assignee: Josef Kopriva Fix For: 4.14.0.AM1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

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

by André Dietisheim (Jira)

[ https://issues.redhat.com/browse/JBIDE-26899?page=com.atlassian.jira.plug... ] André Dietisheim updated JBIDE-26899: ------------------------------------- Sprint: devex #174 Oct 2019, devex #175 Nov 2019, devex #176 Nov/Dec 2019, devex #178 Jan 2020 (was: devex #174 Oct 2019, devex #175 Nov 2019, devex #176 Nov/Dec 2019) > 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: 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)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26915) CDK is up and running but OpenShift is unreachable Error dialog

by André Dietisheim (Jira)

[ https://issues.redhat.com/browse/JBIDE-26915?page=com.atlassian.jira.plug... ] André Dietisheim updated JBIDE-26915: ------------------------------------- Sprint: devex #178 Jan 2020 > CDK is up and running but OpenShift is unreachable Error dialog > --------------------------------------------------------------- > > Key: JBIDE-26915 > URL: https://issues.redhat.com/browse/JBIDE-26915 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift > Affects Versions: 4.13.0.Final > Environment: Fedora 29, Java 11 > Reporter: Ondrej Dockal > Assignee: André Dietisheim > Priority: Major > Fix For: 4.14.0.AM1 > > > In openshift rest client library we should avoid trying to add an authentication parts into http request when trying to check Openshift 3.11 reachability on https://server:port/healthz endpoint. > This should be done on this [line|https://github.com/openshift/openshift-restclient-java/blob/master/s...]. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 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 January 2020