Re: [jetty-dev] servlet-api repackaging

[Joakim Erdfelt <joakim@xxxxxxxxxxx>]

The history of the servlet artifact that was deployed to maven central is that it was designed to be consumed by webapps for making servlet applications.

The servers out there always had to make their own Servlet artifact jar, complete with the details that the server needs (eg: the schemas)

(Every server did this, you can even find all of the Jetty Servlet API jars between Servlet 2.0 and 5.0 if you look)

This means that up to Servlet 5.0 the Jakarta Servlet API artifact is for webapps, not servers.

When Servlet 6.0 came around, this history was broken for the first time, and now the Servlet API artifact contains all that's needed for both servers and webapps.

Since you are packaging for a Server, you are discovering this history.

Joakim Erdfelt / joakim@xxxxxxxxxxx

On Mon, Apr 24, 2023 at 6:49 AM Eirik Bjørsnøs <eirbjo@xxxxxxxxx> wrote:

That standard artifact is also missing the required schemas.

Something both the Jetty Servlet 5.0 module and Standard Jakarta Servlet 6.0 module have fixed.

Unfortunately, the automatic-module-name alone is insufficient to address this flaw in the Standard Jakarta Servlet 5.0 module.

Good that Jakarta Servlet 6.0 fixed this. Sounds like an oversight which could deserve a maintenance release of 5.

Anyhow, I can happily report back that with a little dependency juggling to work with the .ee10 Maven coordinates, Jetty 12 now works fine in my Java module project again.

Eirik.

_______________________________________________
jetty-dev mailing list
jetty-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jetty-dev