<div dir="ltr">This will get to Marek <span style="color:rgb(0,0,0);font-family:Arial,FreeSans,Helvetica,sans-serif;font-size:13px;line-height:17px;text-align:right">Novotny</span>, but he'll definitely be the one to ask.</div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jul 11, 2013 at 8:43 AM, Scott Marlow <span dir="ltr"><<a href="mailto:smarlow@redhat.com" target="_blank">smarlow@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<a href="https://issues.jboss.org/browse/JASSIST-206" target="_blank">https://issues.jboss.org/browse/JASSIST-206</a> is about a Javassist 3.18.0<br>
signature change that broke Seam 2.x applications.<br>
<br>
Could someone let me know if the Seam 2.x testsuite also hits the same<br>
regression when using Javassist 3.18.0?<br>
<br>
I'm trying to answer a related question about how we can tell if a<br>
patched Javassist 3.15.x still works with Seam 2.x applications. If<br>
running the Seam 2.x testsuite hits the JASSIST-206, it might be good<br>
for us to run the Seam 2.x testsuite after patching/upgrading Javassist.<br>
<br>
Thanks for your advise.<br>
<br>
Scott<br>
_______________________________________________<br>
seam-dev mailing list<br>
<a href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr">Jason Porter<br><a href="http://en.gravatar.com/lightguardjp" target="_blank">http://en.gravatar.com/lightguardjp</a><br></div>
</div>