[
https://issues.jboss.org/browse/JBIDE-26750?page=com.atlassian.jira.plugi...
]
Jeff MAURY updated JBIDE-26750:
-------------------------------
Sprint: devex #172 Sep 2019, devex #173 Oct 2019, devex #174 Oct 2019 (was: devex
#172 Sep 2019, devex #173 Oct 2019)
Update CDI.itests to run on java 11 and add some parameters to the
pom.xml
--------------------------------------------------------------------------
Key: JBIDE-26750
URL:
https://issues.jboss.org/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.13.0.Final
*Description of the task from [~odockal]:*
As I said some time ago, would be awesome to also have test project running on Java 11 in
case that test are running on machine with jdk 11. Also, I can see that this condition
repeats in every class, do you dare to extract it somewhere else and just call in
@requirementResctriction annotated method?
Let's put it into some utility class, that's an easiest solution.
Update:
I can image that server family and version would be parametrized in pom. One could have
parameter ie. server.family and server.version and so any update to server and its version
could happen in one place at once.
And you can run test for both server eap and wildfly driven by param in jenkins.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)