[JBoss JIRA] (JBIDE-26787) Several tests in examples.wildfly.itests are failing due to "Exception during sync execution in UI thread"
by Zbyněk Červinka (Jira)
[ https://issues.redhat.com/browse/JBIDE-26787?page=com.atlassian.jira.plug... ]
Zbyněk Červinka edited comment on JBIDE-26787 at 1/7/20 4:14 AM:
-----------------------------------------------------------------
h1. *I have additional info to this issue:*
I made second unsuccessful attempt to fix this issue. I have tried to go deeper in RedDeer, I edited the org.eclipse.reddeer.eclipse.ui.problems.Problem java class and I have added the *problemsView.activate();* statement into the *getCell()* method as it is captured on the picture below.
*Performed changes (output from the git diff):*
!second_unsuccessful_attempt_to_fix_this_issue.png|thumbnail!
was (Author: zcervink):
h1. *I have additional info to this issue:*
I made second unsuccessful attempt to fix this issue. Now I tried to go deeper in RedDeer, I edited the org.eclipse.reddeer.eclipse.ui.problems.Problem java class and I have added the problemsView.activate(); statement to the getCell() method as it is captured on the picture below.
*Performed changes (output from the git diff):*
!second_unsuccessful_attempt_to_fix_this_issue.png|thumbnail!
> Several tests in examples.wildfly.itests are failing due to "Exception during sync execution in UI thread"
> -----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26787
> URL: https://issues.redhat.com/browse/JBIDE-26787
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: integration-tests, project-examples
> Affects Versions: 4.13.0.AM1
> Environment: All, tests are failing sporadically.
> Reporter: Zbyněk Červinka
> Assignee: Zbyněk Červinka
> Priority: Major
> Attachments: first_unsuccessful_attempt_to_fix_this_issue.png, second_unsuccessful_attempt_to_fix_this_issue.png
>
>
> Several tests in examples.wildfly.itests are failing due to "Exception during sync execution in UI thread"
> h2. *Jenkins:*
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples...
> h2. *Stack Trace:*
> org.eclipse.reddeer.common.exception.RedDeerException: Exception during sync execution in UI thread
> at org.jboss.tools.examples.ui.bot.test.integration.WildFlyImportQuickstartsTest.quickstartTest(WildFlyImportQuickstartsTest.java:62)
> Caused by: org.eclipse.swt.SWTException: Widget is disposed
> h2. *Standard Error:*
> org.eclipse.reddeer.common.exception.RedDeerException: Exception during sync execution in UI thread
> at org.eclipse.reddeer.common.util.Display.handleErrorOccured(Display.java:112)
> at org.eclipse.reddeer.common.util.Display.syncExec(Display.java:84)
> at org.eclipse.reddeer.core.handler.TreeItemHandler.getText(TreeItemHandler.java:68)
> at org.eclipse.reddeer.swt.impl.tree.AbstractTreeItem.getCell(AbstractTreeItem.java:77)
> at org.eclipse.reddeer.eclipse.ui.problems.Problem.getCell(Problem.java:68)
> at org.eclipse.reddeer.eclipse.ui.markers.AbstractMarker.getDescription(AbstractMarker.java:43)
> at org.jboss.tools.central.reddeer.api.ExamplesOperator.getAllWarnings(ExamplesOperator.java:225)
> at org.jboss.tools.examples.ui.bot.test.integration.AbstractImportQuickstartsTest.checkForWarnings(AbstractImportQuickstartsTest.java:375)
> at org.jboss.tools.examples.ui.bot.test.integration.AbstractImportQuickstartsTest.runQuickstarts(AbstractImportQuickstartsTest.java:283)
> at org.jboss.tools.examples.ui.bot.test.integration.WildFlyImportQuickstartsTest.quickstartTest(WildFlyImportQuickstartsTest.java:62)
> at jdk.internal.reflect.GeneratedMethodAccessor185.invoke(Unknown Source)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>
> ...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (JBIDE-26787) Several tests in examples.wildfly.itests are failing due to "Exception during sync execution in UI thread"
by Zbyněk Červinka (Jira)
[ https://issues.redhat.com/browse/JBIDE-26787?page=com.atlassian.jira.plug... ]
Zbyněk Červinka edited comment on JBIDE-26787 at 1/7/20 4:15 AM:
-----------------------------------------------------------------
h1. *I have additional info to this issue:*
I made second unsuccessful attempt to fix this issue. I have tried to go deeper in RedDeer, I edited the org.eclipse.reddeer.eclipse.ui.problems.Problem java class and I have added the *problemsView.activate();* statement into the *getCell()* method as it is captured on the picture below.
*Performed changes (output from the git diff):*
!second_unsuccessful_attempt_to_fix_this_issue.png|thumbnail!
*Result of my trial:* Issue still remains, changes did not fix the issue.
was (Author: zcervink):
h1. *I have additional info to this issue:*
I made second unsuccessful attempt to fix this issue. I have tried to go deeper in RedDeer, I edited the org.eclipse.reddeer.eclipse.ui.problems.Problem java class and I have added the *problemsView.activate();* statement into the *getCell()* method as it is captured on the picture below.
*Performed changes (output from the git diff):*
!second_unsuccessful_attempt_to_fix_this_issue.png|thumbnail!
> Several tests in examples.wildfly.itests are failing due to "Exception during sync execution in UI thread"
> -----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26787
> URL: https://issues.redhat.com/browse/JBIDE-26787
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: integration-tests, project-examples
> Affects Versions: 4.13.0.AM1
> Environment: All, tests are failing sporadically.
> Reporter: Zbyněk Červinka
> Assignee: Zbyněk Červinka
> Priority: Major
> Attachments: first_unsuccessful_attempt_to_fix_this_issue.png, second_unsuccessful_attempt_to_fix_this_issue.png
>
>
> Several tests in examples.wildfly.itests are failing due to "Exception during sync execution in UI thread"
> h2. *Jenkins:*
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples...
> h2. *Stack Trace:*
> org.eclipse.reddeer.common.exception.RedDeerException: Exception during sync execution in UI thread
> at org.jboss.tools.examples.ui.bot.test.integration.WildFlyImportQuickstartsTest.quickstartTest(WildFlyImportQuickstartsTest.java:62)
> Caused by: org.eclipse.swt.SWTException: Widget is disposed
> h2. *Standard Error:*
> org.eclipse.reddeer.common.exception.RedDeerException: Exception during sync execution in UI thread
> at org.eclipse.reddeer.common.util.Display.handleErrorOccured(Display.java:112)
> at org.eclipse.reddeer.common.util.Display.syncExec(Display.java:84)
> at org.eclipse.reddeer.core.handler.TreeItemHandler.getText(TreeItemHandler.java:68)
> at org.eclipse.reddeer.swt.impl.tree.AbstractTreeItem.getCell(AbstractTreeItem.java:77)
> at org.eclipse.reddeer.eclipse.ui.problems.Problem.getCell(Problem.java:68)
> at org.eclipse.reddeer.eclipse.ui.markers.AbstractMarker.getDescription(AbstractMarker.java:43)
> at org.jboss.tools.central.reddeer.api.ExamplesOperator.getAllWarnings(ExamplesOperator.java:225)
> at org.jboss.tools.examples.ui.bot.test.integration.AbstractImportQuickstartsTest.checkForWarnings(AbstractImportQuickstartsTest.java:375)
> at org.jboss.tools.examples.ui.bot.test.integration.AbstractImportQuickstartsTest.runQuickstarts(AbstractImportQuickstartsTest.java:283)
> at org.jboss.tools.examples.ui.bot.test.integration.WildFlyImportQuickstartsTest.quickstartTest(WildFlyImportQuickstartsTest.java:62)
> at jdk.internal.reflect.GeneratedMethodAccessor185.invoke(Unknown Source)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>
> ...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (JBIDE-26787) Several tests in examples.wildfly.itests are failing due to "Exception during sync execution in UI thread"
by Zbyněk Červinka (Jira)
[ https://issues.redhat.com/browse/JBIDE-26787?page=com.atlassian.jira.plug... ]
Zbyněk Červinka commented on JBIDE-26787:
-----------------------------------------
h1. *I have additional info to this issue:*
I made second unsuccessful attempt to fix this issue. Now I tried to go deeper in RedDeer, I edited the org.eclipse.reddeer.eclipse.ui.problems.Problem java class and I have added the problemsView.activate(); statement to the getCell() method as it is captured on the picture below.
*Performed changes (output from the git diff):*
!second_unsuccessful_attempt_to_fix_this_issue.png|thumbnail!
> Several tests in examples.wildfly.itests are failing due to "Exception during sync execution in UI thread"
> -----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26787
> URL: https://issues.redhat.com/browse/JBIDE-26787
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: integration-tests, project-examples
> Affects Versions: 4.13.0.AM1
> Environment: All, tests are failing sporadically.
> Reporter: Zbyněk Červinka
> Assignee: Zbyněk Červinka
> Priority: Major
> Attachments: first_unsuccessful_attempt_to_fix_this_issue.png, second_unsuccessful_attempt_to_fix_this_issue.png
>
>
> Several tests in examples.wildfly.itests are failing due to "Exception during sync execution in UI thread"
> h2. *Jenkins:*
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples...
> h2. *Stack Trace:*
> org.eclipse.reddeer.common.exception.RedDeerException: Exception during sync execution in UI thread
> at org.jboss.tools.examples.ui.bot.test.integration.WildFlyImportQuickstartsTest.quickstartTest(WildFlyImportQuickstartsTest.java:62)
> Caused by: org.eclipse.swt.SWTException: Widget is disposed
> h2. *Standard Error:*
> org.eclipse.reddeer.common.exception.RedDeerException: Exception during sync execution in UI thread
> at org.eclipse.reddeer.common.util.Display.handleErrorOccured(Display.java:112)
> at org.eclipse.reddeer.common.util.Display.syncExec(Display.java:84)
> at org.eclipse.reddeer.core.handler.TreeItemHandler.getText(TreeItemHandler.java:68)
> at org.eclipse.reddeer.swt.impl.tree.AbstractTreeItem.getCell(AbstractTreeItem.java:77)
> at org.eclipse.reddeer.eclipse.ui.problems.Problem.getCell(Problem.java:68)
> at org.eclipse.reddeer.eclipse.ui.markers.AbstractMarker.getDescription(AbstractMarker.java:43)
> at org.jboss.tools.central.reddeer.api.ExamplesOperator.getAllWarnings(ExamplesOperator.java:225)
> at org.jboss.tools.examples.ui.bot.test.integration.AbstractImportQuickstartsTest.checkForWarnings(AbstractImportQuickstartsTest.java:375)
> at org.jboss.tools.examples.ui.bot.test.integration.AbstractImportQuickstartsTest.runQuickstarts(AbstractImportQuickstartsTest.java:283)
> at org.jboss.tools.examples.ui.bot.test.integration.WildFlyImportQuickstartsTest.quickstartTest(WildFlyImportQuickstartsTest.java:62)
> at jdk.internal.reflect.GeneratedMethodAccessor185.invoke(Unknown Source)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>
> ...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (JBIDE-26787) Several tests in examples.wildfly.itests are failing due to "Exception during sync execution in UI thread"
by Zbyněk Červinka (Jira)
[ https://issues.redhat.com/browse/JBIDE-26787?page=com.atlassian.jira.plug... ]
Zbyněk Červinka updated JBIDE-26787:
------------------------------------
Attachment: second_unsuccessful_attempt_to_fix_this_issue.png
> Several tests in examples.wildfly.itests are failing due to "Exception during sync execution in UI thread"
> -----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26787
> URL: https://issues.redhat.com/browse/JBIDE-26787
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: integration-tests, project-examples
> Affects Versions: 4.13.0.AM1
> Environment: All, tests are failing sporadically.
> Reporter: Zbyněk Červinka
> Assignee: Zbyněk Červinka
> Priority: Major
> Attachments: first_unsuccessful_attempt_to_fix_this_issue.png, second_unsuccessful_attempt_to_fix_this_issue.png
>
>
> Several tests in examples.wildfly.itests are failing due to "Exception during sync execution in UI thread"
> h2. *Jenkins:*
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples...
> h2. *Stack Trace:*
> org.eclipse.reddeer.common.exception.RedDeerException: Exception during sync execution in UI thread
> at org.jboss.tools.examples.ui.bot.test.integration.WildFlyImportQuickstartsTest.quickstartTest(WildFlyImportQuickstartsTest.java:62)
> Caused by: org.eclipse.swt.SWTException: Widget is disposed
> h2. *Standard Error:*
> org.eclipse.reddeer.common.exception.RedDeerException: Exception during sync execution in UI thread
> at org.eclipse.reddeer.common.util.Display.handleErrorOccured(Display.java:112)
> at org.eclipse.reddeer.common.util.Display.syncExec(Display.java:84)
> at org.eclipse.reddeer.core.handler.TreeItemHandler.getText(TreeItemHandler.java:68)
> at org.eclipse.reddeer.swt.impl.tree.AbstractTreeItem.getCell(AbstractTreeItem.java:77)
> at org.eclipse.reddeer.eclipse.ui.problems.Problem.getCell(Problem.java:68)
> at org.eclipse.reddeer.eclipse.ui.markers.AbstractMarker.getDescription(AbstractMarker.java:43)
> at org.jboss.tools.central.reddeer.api.ExamplesOperator.getAllWarnings(ExamplesOperator.java:225)
> at org.jboss.tools.examples.ui.bot.test.integration.AbstractImportQuickstartsTest.checkForWarnings(AbstractImportQuickstartsTest.java:375)
> at org.jboss.tools.examples.ui.bot.test.integration.AbstractImportQuickstartsTest.runQuickstarts(AbstractImportQuickstartsTest.java:283)
> at org.jboss.tools.examples.ui.bot.test.integration.WildFlyImportQuickstartsTest.quickstartTest(WildFlyImportQuickstartsTest.java:62)
> at jdk.internal.reflect.GeneratedMethodAccessor185.invoke(Unknown Source)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>
> ...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (JBIDE-26992) Implement Javadoc retrieval
by Jeff MAURY (Jira)
Jeff MAURY created JBIDE-26992:
----------------------------------
Summary: Implement Javadoc retrieval
Key: JBIDE-26992
URL: https://issues.redhat.com/browse/JBIDE-26992
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: quarkus
Affects Versions: 4.14.0.AM1
Reporter: Jeff MAURY
Assignee: Jeff MAURY
Fix For: 4.14.0.AM1
The Kubernetes provider requires to retrieve the Javadoc from associated dekorate annotations as descriptions for the items.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[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:
------------------------------------
Description:
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)
was:
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)
> 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, 3 months
[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 updated JBIDE-26991:
------------------------------------
Description:
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)
was:
* CDI version in cdi.itests has been updated from version 1.1 to version 1.2
* 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)
> 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, 3 months
[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 updated JBIDE-26991:
------------------------------------
Description:
* CDI version in cdi.itests has been updated from version 1.1 to version 1.2
* 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
was:
* CDI version in cdi.itests has been updated from version 1.1 to version 1.2
* 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
> 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
>
>
> * CDI version in cdi.itests has been updated from version 1.1 to version 1.2
> * 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, 3 months
[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 updated JBIDE-26991:
------------------------------------
Description:
* CDI version in cdi.itests has been updated from version 1.1 to version 1.2
* 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)
was:
* CDI version in cdi.itests has been updated from version 1.1 to version 1.2
* 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
> 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
>
>
> * CDI version in cdi.itests has been updated from version 1.1 to version 1.2
> * 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, 3 months