JBIDE-26991 - Update cdi.itests class and method names to contain the "CDI12" string instead of containing the "CDI11" string #1971
Conversation
zcervink
force-pushed
the
JBIDE-26991
branch
3 times, most recently
from
043ca1d
to
f31b731
Compare
… "CDI12" string instead of containing the "CDI11" string Signed-off-by: Zbynek Cervinka <zcervink@redhat.com>
zcervink
changed the title
zcervink
changed the title
zcervink
changed the title
|
Update on this PR - after some additional refactoring (Sonar issues) I have new Jenkins runs: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/cdi10.itests/620/ |
|
@zcervink Seems ok. I will merge this right now. But I have a another task. I noticed that weld module used references older CDI specs. (1.0 and 1.1). I think it would be great to add another weld versions and use them in testing different CDI versions. I would use this WF -> Weld/CDI specs reference table. Then I would use WF version/CDI version number to differentiate between weld implementations used. Let's create another jira for this. |
JIRA: https://issues.redhat.com/browse/JBIDE-26991
JENKINS CDI 1.0: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/cdi10.itests/618/
JENKINS CDI 1.2: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/cdi12.itests/724/
JENKINS CDI 2.0: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/cdi20.itests/397/
Signed-off-by: Zbynek Cervinka zcervink@redhat.com
Please review @jkopriva @odockal