<div dir="ltr">Flavia, if you have a branch I can start testing it today.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Aug 3, 2020 at 8:35 AM Matej Novotny <<a href="mailto:manovotn@redhat.com">manovotn@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Yeah, I had an email conversation with her and few others recently.<br>
>From what I understood, it should be ready to go, we just need to test it locally somehow.<br>
Ccing Flavia as well.<br>
<br>
Matej<br>
<br>
----- Original Message -----<br>
> From: "Scott Stark" <<a href="mailto:sstark@redhat.com" target="_blank">sstark@redhat.com</a>><br>
> To: "Matej Novotny" <<a href="mailto:manovotn@redhat.com" target="_blank">manovotn@redhat.com</a>><br>
> Cc: "weld-dev" <<a href="mailto:weld-dev@lists.jboss.org" target="_blank">weld-dev@lists.jboss.org</a>><br>
> Sent: Monday, August 3, 2020 3:18:54 PM<br>
> Subject: Re: [weld-dev] Cleaning up weld core master<br>
> <br>
> Ok, I'll sink my changes with yours. I don't see any work in the<br>
> undertow github on a ee9 release, so perhaps it is still local to Flavia.<br>
> <br>
> On Mon, Aug 3, 2020 at 1:26 AM Matej Novotny <<a href="mailto:manovotn@redhat.com" target="_blank">manovotn@redhat.com</a>> wrote:<br>
> <br>
> > Hi,<br>
> ><br>
> > sorry for the delay, I was on PTO.<br>
> > Here is a summary of where we stand ATM.<br>
> ><br>
> > There is a Weld issue for this[1] and some progress on my own branch[2].<br>
> > The only thing I was really waiting for is Undertow release, which I have<br>
> > been told by Flavia is to be released soon (actually might be out at this<br>
> > point, have to check that out).<br>
> > Otherwise the branch removed these old artifacts and updated to newer<br>
> > jetty and tomcat versions. Testing is working on a Tomcat arq. adapter,<br>
> > Jetty is still broken.<br>
> > There is also a glitch with one test due to missing released mojarra<br>
> > version in central[3].<br>
> ><br>
> > I have put that up as a draft so you can see the progress and base<br>
> > anything off that.<br>
> > See <a href="https://github.com/weld/core/pull/2008" rel="noreferrer" target="_blank">https://github.com/weld/core/pull/2008</a><br>
> ><br>
> > Things to resolve there are:<br>
> > * Undertow support, we need to check if the release is out and adapt it<br>
> > * Update jetty arq adapter to EE 9 version[4] which I frankly don't yet<br>
> > know how to do since some of their APIs have changed<br>
> > * Temporarily disable and track (via issue) the failing test due to<br>
> > aforementioned mojarra issue[3]<br>
> > * ?? maybe something else.. ?<br>
> ><br>
> > Feel free to tackle any of the above if you feel like it. I have yet to<br>
> > recover from a pile of unread mail and messages before I can get to this<br>
> > anyway.<br>
> ><br>
> > > We don't have one for undertow yet, so I will disable that for now.<br>
> ><br>
> > This would require to either comment out several classes and tests or<br>
> > remove them temporarily.<br>
> > I've talked to Undertow team and was told that they are planning to<br>
> > release EE 9 version for us rather than see us evict undertow from<br>
> > supported servlets (even temporarily).<br>
> ><br>
> > > > I'm going through testing the current CDI 3.0.0-RC1 TCK in preparation<br>
> > for<br>
> > > the final release<br>
> ><br>
> > Servlet bits shouldn't block you from executing CDI TCK.<br>
> ><br>
> > Regards<br>
> > Matej<br>
> ><br>
> ><br>
> > _________________________________________________________________________________-<br>
> > [1] <a href="https://issues.redhat.com/browse/WELD-2630" rel="noreferrer" target="_blank">https://issues.redhat.com/browse/WELD-2630</a><br>
> > [2] <a href="https://github.com/manovotn/core/tree/weld2630" rel="noreferrer" target="_blank">https://github.com/manovotn/core/tree/weld2630</a><br>
> > [3] <a href="https://github.com/eclipse-ee4j/mojarra/issues/4729" rel="noreferrer" target="_blank">https://github.com/eclipse-ee4j/mojarra/issues/4729</a><br>
> > [4] <a href="https://github.com/arquillian/arquillian-container-jetty/issues/43" rel="noreferrer" target="_blank">https://github.com/arquillian/arquillian-container-jetty/issues/43</a><br>
> ><br>
> ><br>
> > ----- Original Message -----<br>
> > > From: "Scott Stark" <<a href="mailto:sstark@redhat.com" target="_blank">sstark@redhat.com</a>><br>
> > > To: "weld-dev" <<a href="mailto:weld-dev@lists.jboss.org" target="_blank">weld-dev@lists.jboss.org</a>><br>
> > > Sent: Thursday, July 30, 2020 9:02:56 PM<br>
> > > Subject: [weld-dev] Cleaning up weld core master<br>
> > ><br>
> > > I'm going through testing the current CDI 3.0.0-RC1 TCK in preparation<br>
> > for<br>
> > > the final release, and there are old integrations like<br>
> > > org.jboss.weld.environment.gwtdev that rely on a jetty-6 release for GWT<br>
> > > stuff. This will not work under the EE9 api change, so I'm going to<br>
> > remove<br>
> > > it.<br>
> > ><br>
> > > I'm also trying to update the tomcat and jetty support using the current<br>
> > EE 9<br>
> > > based releases.<br>
> > ><br>
> > > We don't have one for undertow yet, so I will disable that for now.<br>
> > ><br>
> > > Is there any other cleanup/reorg we want to do as part of this?<br>
> > ><br>
> > ><br>
> > > _______________________________________________<br>
> > > weld-dev mailing list<br>
> > > <a href="mailto:weld-dev@lists.jboss.org" target="_blank">weld-dev@lists.jboss.org</a><br>
> > > <a href="https://lists.jboss.org/mailman/listinfo/weld-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/weld-dev</a><br>
> ><br>
> ><br>
> <br>
<br>
</blockquote></div>