@Dennis: the point is more about not encouraging users to consume it, tomcat has no big issue integrating the project as it is in its own code base but as an servlet API user, importing it means either to not use servlet 3 api or to not use fileupload but both together can become a nightmare when mixed thru libraries so since it is not needed on end users side now maybe it is time to not do a v2 and let tomcat handle the impl as part of the tomat project. Guess it was the main point and I think it makes sense.
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://rmannibucau.metawerx.net/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/application-development/java-ee-8-high-performance> Le dim. 9 juil. 2023 à 19:53, Dennis Kieselhorst <d...@apache.org> a écrit : > It's not redundant as Servlet API is just the API and commons-fileupload > offers a server-side implementation that even Tomcat could use (forked code > lives here > https://github.com/apache/tomcat/tree/main/java/org/apache/tomcat/util/http/fileupload > ). > > See also: https://issues.apache.org/jira/browse/FILEUPLOAD-309 > > Best, > Dennis > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
