[
https://issues.apache.org/jira/browse/FILEUPLOAD-309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17677337#comment-17677337
]
Flying Wolf edited comment on FILEUPLOAD-309 at 1/16/23 11:53 AM:
------------------------------------------------------------------
[[email protected]]
The current big problem with FileUpload, where is issue is about, is this:
At 10 September 2019 the "Java Servlet" api was renamed to "Jakarta Servlet",
starting from version 4.0.3.
At 9 October 2020, with the release of Jakarta Servlet 5.0, the API moved from
package `javax.servlet` to `jakarta.servlet`.
This package change has big consequences when a project (such as Wicket) wants
to update its old Servlet dependency to the new Jakarta Servlet 5.0 API package
(jakarta.servlet), but the project (Wicket) also depends on a project
(FileUpload) that is still using the old package (javax.servlet). This causes
the project (Wicket) to be unable to update to a new Servlet version.
If Wicket would stick to the old Java Servlet version that FileUpload
automatically and unknowingly is enforcing to projects since 9 October 2020,
then this also causes other dependency problems for Wicket. For example, Spring
Framework 6 also moved from Java Servlet to Jakarta Servlet. Because FileUpload
is enforcing other projects to stay with the old Java Servlet spec, other
projects (such as Wicket) won't be able to update to Spring Framework 6. This
will become an ever bigger issue when Spring Framework 5 gets end-of-life in
2024. Then projects are forced to use outdated insecure Spring version, or they
have to fully drop the usage of FileUpload.
So FileUpload is enforcing projects to use an old Servlet spec, which causes
major problems for these projects to be able to update important dependencies
(Jakarta Servlet and Spring Framework).
Whereas the solution in FileUpload to solve this big problem, is really simple:
FileUpload only needs to update it dependency (javax.servlet:servlet-api:2.4
provided dependency) to a Jakarta Servlet depedency (for example
jakarta.servlet:jakarta.servlet-api:6.0.0). Which means changing some simple
import statements from "javax.servlet" to "jakarta.servlet".
This simple fix would help projects that depend on FileUpload, a lot.
was (Author: flyingwolf):
[[email protected]]
The current big problem with FileUpload, where is issue is about, is this:
At 10 September 2019 the "Java Servlet" api was renamed to "Jakarta Servlet",
starting from version 4.0.3.
At 9 October 2020, with the release of Jakarta Servlet 5.0, the API moved from
package `javax.servlet` to `jakarta.servlet`.
This package change has big consequences when a project (such as Wicket) wants
to update its old Servlet dependency to the new Jakarta Servlet 5.0 API package
(jakarta.servlet), but the project (Wicket) also depends on a project
(FileUpload) that is still using the old package (javax.servlet). This causes
the project (Wicket) to be unable to update to a new Servlet version.
If Wicket would stick to the old Java Servlet version that FileUpload
automatically and unknowingly is enforcing to projects since 10 September 2019,
then this also causes other dependency problems for Wicket. For example, Spring
Framework 6 also moved from Java Servlet to Jakarta Servlet. Because FileUpload
is enforcing other projects to stay with the old Java Servlet spec, other
projects (such as Wicket) won't be able to update to Spring Framework 6. This
will become an ever bigger issue when Spring Framework 5 gets end-of-life in
2024. Then projects are forced to use outdated insecure Spring version, or they
have to fully drop the usage of FileUpload.
So FileUpload is enforcing projects to use an old Servlet spec, which causes
major problems for these projects to be able to update important dependencies
(Jakarta Servlet and Spring Framework).
Whereas the solution in FileUpload to solve this big problem, is really simple:
FileUpload only needs to update it dependency (javax.servlet:servlet-api:2.4
provided dependency) to a Jakarta Servlet depedency (for example
jakarta.servlet:jakarta.servlet-api:6.0.0). Which means changing some simple
import statements from "javax.servlet" to "jakarta.servlet".
This simple fix would help projects that depend on FileUpload, a lot.
> Release version 2.0.0
> ---------------------
>
> Key: FILEUPLOAD-309
> URL: https://issues.apache.org/jira/browse/FILEUPLOAD-309
> Project: Commons FileUpload
> Issue Type: Wish
> Reporter: Thiago Henrique Hupner
> Priority: Major
>
> At Piranha, we've migrated to use the new Jakarta namespace.
> One of our dependencies is the Commons File Upload, but the latest version
> available is 1.4.
> Looking around at the source code, I've found that the code is already
> prepared for the new Jakarta namespace.
> So, I want to know if there's a plan to release a new version soon. Or at
> least a 2.0.0 milestone.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
