We have a 4.0.0.Alpha3 in maven central, but there is no link under:
How does that get created? We need one as that is what is being used for
the CDI 3.0
compatibility certification request.
Thanks Flavia, I'll start working on it this afternoon.
On Tue, Aug 4, 2020 at 3:57 AM Flavia Rainone <frainone(a)redhat.com> wrote:
> The code is here:
> You just need to fetch that branch and follow the steps:
> - fetch Batavia project that is used to transform bytes and build it:
> - build Undertow with maven clean install -DskipTests (or do not skip
> them, but keep in mind they take quite a long time to run)
> - then use the generated artifacts as dependencies wherever needed:
> Since these artifacts are untested, probably you will come back to me
> with feedback if you find any trouble using them. :-)
> Feel free to ping me at any time.
> As soon as this passes, I'll deploy those artifacts to Nexus.
On Mon, Aug 3, 2020 at 8:55 AM Flavia Rainone <frainone(a)redhat.com> wrote:
> That's great!
> I am using a generated jar by Batavia project. You will need to checkout
> that project as well. But, first, I need to do some final adjustments to my
> pom transformer and then I'll push the code to github and give you all the
> Flavia Rainone
> Principal Software Engineer
> Red Hat <https://www.redhat.com>
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
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?