Makes sense.

Seeing ValidationTest-AS7 brings something else to mind. Once upon a time, we were targeting both AS7 and WF8, and they had very different Hibernate Validator (HV) versions. In particular, AS7 had HV4, based on Bean Validation spec 1.0 and WF8 had HV5, based on Bean Validation spec 1.1. To accommodate both, I created an adaptation layer (GeneralValidator) and two submodules: resteasy-hibernatevalidator-provider for HV4 and resteasy-validator-provider-11 for HV5. We could deprecate resteasy-hibernatevalidator-provider now.

-Ron

Folks,
we have a bunch of JBoss AS7 specific tests in the project. I'm inclined 
to removing them on master, especially wherever they're duplicated by 
equivalent tests against WFLY. See for instance 
https://github.com/resteasy/Resteasy/pull/819, in particular 
https://github.com/resteasy/Resteasy/pull/819/commits/63a4f1a4603a675699fe27a41b3ed1481e855d0f 
.
If you have any comment, please just let me know, otherwise I'll proceed 
later today.

Generally speaking, moving forward, we should "support" the latest 
versions only of WildFly; for example, in JBossWS we test against the 
latest 3 released WildFly versions, plus current master. We could 
eventually do something similar in RESTEasy.

Cheers
Alessio

-- 
My company's smarter than your company (unless you work for Red Hat)