Hi Gary

Thanks for your reply. Since there is no planned date for a stable release and 
we need a production-ready library in January 2024, we decided to switch to 
another solution.

Thanks,
Paolo


-----Ursprüngliche Nachricht-----
Von: Gary Gregory <garydgreg...@gmail.com>
Gesendet: Montag, 11. Dezember 2023 21:33
An: Commons Users List <user@commons.apache.org>
Betreff: Re: Release date for commons-fileupload2-jakarta?

[Sie erhalten nicht häufig E-Mails von garydgreg...@gmail.com. Weitere 
Informationen, warum dies wichtig ist, finden Sie unter 
https://aka.ms/LearnAboutSenderIdentification ]

First, this needs fixing:

https://github.com/apache/commons-fileupload/pull/248

Feel free to provide a fix.

There is no schedule ATM. We would like more testing, hence the M1 milestone 
release to make the jar easily accessible. Do test this version.

We can cut a M2 version once the above PR 248 issue is addressed and code has 
been reviewed again.

TY,
Gary


On Mon, Dec 11, 2023, 9:50 AM Paolo Bazzi <paolo.ba...@bsi-software.com>
wrote:

> Hi All,
>
>
>
> The commons fileupload page [1] lists the 2.0.0-M1 as latest release
> which is Jakarta-ready. This build was published in July 2023 and is
> marked as Milestone build.
>
>
>
> Is there a planned release date for an official, production-ready build?
>
>
>
> Artefact:
>
>
>
> <dependency>
>
>   <groupId>org.apache.commons</groupId>
>
>   <artifactId>commons-fileupload2</artifactId>
>
>   <version>2.0.0-M1</version>
>
> </dependency>
>
>
>
> [1]
> https://gith/
> ub.com%2Fapache%2Fcommons-fileupload%23where-can-i-get-the-latest-rele
> ase&data=05%7C02%7Cpaolo.bazzi%40bsi-software.com%7C7f71f3a29c924a3eae
> be08dbfa887a01%7C26f00d3eed2549d1917420bfdd2a2564%7C1%7C0%7C6383792364
> 49362455%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiL
> CJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=pIJYuWT3AqvLYC%2BL
> RhSja%2F3NyVEQdBtgB8vcLG4ygF0%3D&reserved=0
>
>
>
> Regards,
>
> Paolo
>
>
>

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to