[
https://issues.apache.org/jira/browse/FILEUPLOAD-309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17679081#comment-17679081
]
Flying Wolf commented on FILEUPLOAD-309:
----------------------------------------
[~joc...@apache.org] So the problem with FileUpload is that the Jakarta update
of FileUpload is only available in a snapshot, but not in a stable release.
Large and stable projects, such as Wicket and Vaadin, don't want to rely on
snapshot dependencies as snapshot dependencies should only exist during
development and could be changed at any time, which can cause projects that
depend on it, not to be stable. A released version (a non-snapshot version)
should not rely on any snapshot version, so these projects cannot use the
Jakarta update of FileUpload until it is published in a stable release.
Because stable releases of FileUpload are still enforcing the older non-Jakarta
Servlet namespace, this causes a cascade of transient dependency problems down
the road. For example, Wicket and Vaadin are often used with Spring Framework.
Spring version 6 moved to the new Jakarta namespace, but because FileUpload is
also a dependency, projects that want to move to Spring 6 cannot continue
because FileUpload is still using the non-Jakarta Servlet namespace. Spring 5
will be end-of-life in 2024, which may even cause security problems for
projects if FileUpload doesn't update a stable release to the Jakarta namespace.
So these project (such as Apache Wicket, Vaadin, Piranha, Apache Causeway) are
hoping for a non-snapshot release.
> 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)
