Yeah, I had an email conversation with her and few others recently.
>From what I understood, it should be ready to go, we just need to test it locally somehow.
Ccing Flavia as well.

Matej

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