<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, May 5, 2016 at 3:58 PM, Marek Kopecky <span dir="ltr"><<a href="mailto:mkopecky@redhat.com" target="_blank">mkopecky@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div text="#000000" bgcolor="#FFFFFF">Is it really necessary to support RESTEasy with JDK7?<br>
For WF10: Java 7 support has been discontinued allowing for deeper
integration with the Java 8 runtime.
</div></blockquote><div><br></div><div>Definitly not anymore, if we go for new major version aka v3 of RestEasy it can easily require Java 8 as minumum.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div text="#000000" bgcolor="#FFFFFF"><span class=""><blockquote type="cite">
<blockquote type="cite">
<pre></pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre>- I would like to see ARQ + WF10+ and get rid of tjws
</pre>
</blockquote>
<pre>Get ridding of TJWS is not practical because it will make the test time
unacceptable. But replacing them with undertow container would be great
:-)
</pre>
</blockquote>
<pre>A lot of tests just don't depend on the environment. I create arquillian
</pre>
</blockquote>
<pre>But there are tests which pass on tjws, but failed with WF10 / EAP7, you can check the jira link I shared in previous email or see below</pre>
</blockquote>
</blockquote>
</span><ul>
<li>I run upstream TS on perf-machine. I build resteasy. Then I
run tests: <br>
</li>
<ul>
<li>Tests tooks 10 minutes.</li>
</ul>
<li>I run qe-internal-resteasy-ts on the same perf-machine.
Qe-internal-resteasy-ts contains all tests from upstream. These
tests are run against EAP.</li>
<ul>
<li>Tests tooks 13 minutes. </li>
</ul>
</ul>
So in my point of view, test time with ARQ + WF10 is definitelly
acceptable.</div></blockquote><div><br>ARQ in general, as we can just configure different profiles for other containers if we want to.<br><br></div><div>Having current mess with each test/ module having their own version of jetty / tjsw is just plain wrong.<br><br></div><div>Also keep in mind that tjsw was never fully tested against servlet TCK, so fixing any tests code for bugs found on uncertifed platform is just wrong.<br></div></div><br><br></div></div>