Move multipart classes to jetty-server #4459
Comments
sbordet
added a commit
that referenced
this issue
Jan 9, 2020
Moved multipart classes to jetty-server. Updated jetty-http's pom.xml and module-info.java removing the dependency on Servlet APIs. Signed-off-by: Simone Bordet <simone.bordet@gmail.com>
sbordet
added a commit
that referenced
this issue
Jan 9, 2020
…t_to_server Fixes #4459 - Move multipart classes to jetty-server.
sbordet
added a commit
that referenced
this issue
Jan 14, 2020
Removed Surefire Plugin configuration no longer needed. Signed-off-by: Simone Bordet <simone.bordet@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Jetty version
10.0.x
Description
Multipart classes are now in
jetty-http, but they are the only ones that require the Servlet API.This makes it non-optimal from the point of view of the JPMS module dependencies, and of course they are not used at all in the client.
I propose that we move these classes to
jetty-server, as it is the only user of the multipart classes.The text was updated successfully, but these errors were encountered: