Planned release of 1.5?

[nrmnrm]

Hi @ste-gr , you have any plans for doing for proper 1.5 release soon? At least the parts we use are currently are all running fine :)

Best regards, Lars

[girgen]

+1

[eagle79]

We'd really like to see this too... though I'd like to see it include PR #53 if possible. I'm migrating some legacy applications to this (as a stopgap for eventual complete replacement) and this project is a godsend. We can go with 1.5.0-RC2, but it always looks better if you're using an officially stable release.

We're in testing with our application against Java 21 and Tomcat 11 (but configured for servlet spec 6.0 in web.xml) and so far I haven't found any issues (at least none caused by weblegacy/struts1!) even though current explicit support stops at Servlet 5.0.

[cincottat]

I am looking to see if there is going to be any effort to bring this to an official release. It seems as though this project has sadly lost most of its traction. One specific blocker involves PR #53 and potential similar updates. The existing commons-fileupload2-2.0.0-M1 is being flagged with a vulnerability, and I would like to be able to move to commons-fileupload2-jakarta-servlet6. @ste-gr, is there any hope of further enhancements to this project or should it be considered a dead repo?

[nrmnrm]

I have forked the repo and fixed outstanding issues, feel free to use it as 1.6 release

[cincottat]

Many thanks for continuing the effort, @nrmnrm ! This is great news.

[TimCincotta]

One question for clarification: Do you intend on formally publishing this on Maven Central? I work in fintech and the application I support requires OSS to be accessible from a public repository.

…

________________________________ From: cincottat ***@***.***> Sent: Monday, June 1, 2026 1:50 PM To: weblegacy/struts1 ***@***.***> Cc: Subscribed ***@***.***> Subject: Re: [weblegacy/struts1] Planned release of 1.5? (Discussion #47) Many thanks for continuing the effort, @nrmnrm<https://github.com/nrmnrm > ! This is great news. — Reply to this email directly, view it on GitHub<#47?email_source=notifications&email_token=AAXDQVQTB2OFWMIUAAW25O345XF7NA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZRGQYDMMJYUZZGKYLTN5XKU43VMJZWG4TJMJSWJJLFOZSW45FMMZXW65DFOJPWG3DJMNVQ#discussioncomment-17140618 >, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAXDQVSQSOKRW7Z456VTE7D45XF7NAVCNFSM6AAAAACZV6ZCFWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTOMJUGA3DCOA >. Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS<https://github.com/notifications/mobile/ios/AAXDQVTSL6Y5G2UOS3CAIA345XF7NA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZRGQYDMMJYUZZGKYLTN5XKU43VMJZWG4TJMJSWJJLFOZSW45FKMZXW65DFOJPWS33T > and Android<https://github.com/notifications/mobile/android/AAXDQVUBRGHIJEL6SGNHMMT45XF7NA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZRGQYDMMJYUZZGKYLTN5XKU43VMJZWG4TJMJSWJJLFOZSW45FOMZXW65DFOJPWC3TEOJXWSZA >. Download it today! You are receiving this because you are subscribed to this thread.Message ID: ***@***.***> The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.

[nrmnrm]

Can:t say, I am not sure what the quality requirements are there and I don't want to take away Stefans work

[ste-gr]

Hi,

I started to prepare version 1.5.0.

Greetings
Stefan

[cincottat]

This is wonderful news, Stefan. May I request that the change Lars did in his fork be considered, re: moving the 1.5.x branch to Jakarta EE 10 (or supporting both EE9 and EE10 versions of the library)?

As a brief backdrop, we have standardized our app on EE10/Servlet 6 and had tested nearly all functionality with the 1.5.0-RC2 branch successfully. However, one function that utilizes commons-fileupload2 threw the exception matching the issue referenced in [#51] by flyingfischer. This has truly been the only EE10-unique situation we have come across when using RC2.

Given that we are in the late stages of this effort, having an EE10 version of this library has become a hard requirement for us, and we are in a bit of a bind.

[cincottat]

Greetings, Stefan. I am just checking to see if you have any ideas on a timeline for your 1.5.0 release, or if you need any assistance.

[ste-gr]

Hi,

I would like to also resolve some open issues:

• html:cancel taglib not working in case of MultipartRequestWrapper #32 & 32 htmlcancel taglib not working in case of multipartrequestwrapper #37
• Character encoding in multipart/form-data #39 & Fix: Character encoding in multipart/form-data #50
• create action optimization #49
• Add security-fix from Lars.

Currently I'm working at tiles-jakarta to fulfill #45 & #46. Here I'm nearly ready.

And after that I'll upgrade to EE10 and include #51.

Greetings
Stefan

[nrmnrm]

Hi Stefan, I have added one more security fix on my fork if you like to include it (or if you like to bump to ee10 as well you can use that too ofc)
Best, Lars

[ste-gr]

Hi Lars,

thank you, I'll add that fix.

Greetings
Stefan