<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Makes sense.</p>
<p>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.</p>
<p>-Ron<br>
</p>
<div class="moz-cite-prefix">On 06/01/2016 05:18 AM, Alessio Soldano
wrote:<br>
</div>
<blockquote cite="mid:574EA851.8050807@redhat.com" type="cite">
<pre wrap="">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
<a class="moz-txt-link-freetext" href="https://github.com/resteasy/Resteasy/pull/819">https://github.com/resteasy/Resteasy/pull/819</a>, in particular
<a class="moz-txt-link-freetext" href="https://github.com/resteasy/Resteasy/pull/819/commits/63a4f1a4603a675699fe27a41b3ed1481e855d0f">https://github.com/resteasy/Resteasy/pull/819/commits/63a4f1a4603a675699fe27a41b3ed1481e855d0f</a>
.
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
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
My company's smarter than your company (unless you work for Red Hat)</pre>
</body>
</html>