RE: RE: [ANNOUNCE] Apache Commons FileUpload 2.0.0-M1

2023-07-21 Thread Eduardo Guadalupe
https://central.sonatype.com/artifact/org.apache.commons/commons-fileupload2/2.0.0-M1 On 2023/07/21 16:27:33 je...@mercedes-benz.com.INVALID wrote: > Hello Gary, > > does that include Milestone releases as well or not? > > Regards > Jeremias > > -Original Message- > From: Gary Gregory

Re: [FileUpload] Major version 2

2023-07-21 Thread Glavo
+1 for Java 17. Glavo On Fri, Jul 21, 2023 at 10:18 PM Gary Gregory wrote: > Now that 2.0.0-M1 is out the door, let's talk about Java platform > requirements. > > I propose that for 2.0.0, FileUpload be bumped from Java 8 to 11, if not > 17. > > If you are going to ask why, see my reply in the

Re: [FileUpload] Major version 2

2023-07-21 Thread Romain Manni-Bucau
+1 for java 17, requirement is java 21 as the new requirement for jakartaee, anything in between is already migrated or will not be migrated so 17 seems already low to me. Romain Manni-Bucau @rmannibucau | Blog | Old Blog

Re: [pool] Another source compatibility break in 2.x

2023-07-21 Thread Phil Steitz
On Fri, Jul 21, 2023 at 5:17 AM Elliotte Rusty Harold wrote: > On Thu, Jul 20, 2023 at 8:27 PM Phil Steitz wrote: > > > > We have a minor source compat break still in 2.x > > > > The change to have BaseGenericObjectPool implement Autocloseable forced > > addition of an abstract close method.

Re: [FileUpload] Major version 2

2023-07-21 Thread Richard Zowalla
From a spec view: Baseline for Jakarta EE 10 would be Java 11. Jakarta EE 9 is still Java 8 (namespace Change only) Gruß Richard Am 21. Juli 2023 18:10:48 MESZ schrieb Elliotte Rusty Harold : >Absolutely not Java 17. There are really big companies still on Java >11, and I have no idea how

RE: [ANNOUNCE] Apache Commons FileUpload 2.0.0-M1

2023-07-21 Thread jeremias.eppler
Hello Gary, does that include Milestone releases as well or not? Regards Jeremias -Original Message- From: Gary Gregory Sent: Friday, 21 July 2023 17:08 To: Commons Developers List Subject: Re: [ANNOUNCE] Apache Commons FileUpload 2.0.0-M1 [**EXTERNAL E-MAIL**] All releases go to

Re: [FileUpload] Major version 2

2023-07-21 Thread Elliotte Rusty Harold
Absolutely not Java 17. There are really big companies still on Java 11, and I have no idea how many smaller ones. There are many still on Java 8. Unless you actually **need** something from Java 11+ I wouldn't bother. On Fri, Jul 21, 2023 at 10:18 AM Gary Gregory wrote: > > Now that 2.0.0-M1

Re: [ANNOUNCE] Apache Commons FileUpload 2.0.0-M1

2023-07-21 Thread Gary Gregory
All releases go to MC. Gary On Fri, Jul 21, 2023, 10:47 wrote: > Hello Gary, > > are you releasing the Apache Commons FileUpload 2.0.0-M1 to Maven Central > as well? > That would make the testing easier. > > Regards > Jeremias > > -Original Message- > From: Gary Gregory > Sent:

Re: [FileUpload] Major version 2

2023-07-21 Thread Maxim Solodovnik
+1 for java17 :) On Fri, 21 Jul 2023 at 21:52, Mark Thomas wrote: > > On 21/07/2023 16:18, Gary Gregory wrote: > > Now that 2.0.0-M1 is out the door, let's talk about Java platform > > requirements. > > > > I propose that for 2.0.0, FileUpload be bumped from Java 8 to 11, if not 17. > > +1 for

Re: [FileUpload] Major version 2

2023-07-21 Thread Mark Thomas
On 21/07/2023 16:18, Gary Gregory wrote: Now that 2.0.0-M1 is out the door, let's talk about Java platform requirements. I propose that for 2.0.0, FileUpload be bumped from Java 8 to 11, if not 17. +1 for Java 17 Mark If you are going to ask why, see my reply in the [pool] thread

RE: [ANNOUNCE] Apache Commons FileUpload 2.0.0-M1

2023-07-21 Thread jeremias.eppler
Hello Gary, are you releasing the Apache Commons FileUpload 2.0.0-M1 to Maven Central as well? That would make the testing easier. Regards Jeremias -Original Message- From: Gary Gregory Sent: Friday, 21 July 2023 15:43 To: Commons Developers List Subject: Re: [ANNOUNCE] Apache

RE: [FileUpload] Major version 2

2023-07-21 Thread jeremias.eppler
Hello Gary, Java 11 should be fine. We need FileUpload 2.0, because we want to upgrade to Spring Boot 3.0 which requires Java 17 and uses JakartaEE: https://github.com/mercedes-benz/sechub/issues/797 Regards Jeremias -Original Message- From: Gary Gregory Sent: Friday, 21 July 2023

[FileUpload] Major version 2

2023-07-21 Thread Gary Gregory
Now that 2.0.0-M1 is out the door, let's talk about Java platform requirements. I propose that for 2.0.0, FileUpload be bumped from Java 8 to 11, if not 17. If you are going to ask why, see my reply in the [pool] thread (https://lists.apache.org/thread/ngyrssxndklltzkoqfqx4n780h4b5vwk) Gary

Re: [ANNOUNCE] Apache Commons FileUpload 2.0.0-M1

2023-07-21 Thread Gary Gregory
This is a milestone release because we might not have the gotten the API just right for a major release. This gives up the opportunity to receive feedback and adjust the API for what will be 2.0.0. All lot of folks will not try a snapshot build, which then leaves us in the dark. WRT to the

RE: [ANNOUNCE] Apache Commons FileUpload 2.0.0-M1

2023-07-21 Thread Christoph Grüninger
Hi Gary! Thank you for this release and thanks to all the diligent contributors! Having a new release with new features, cleaned-up interfaces, and updated dependencies is much appreciated! I also learned from the recent discussion whether FileUpload is still a good idea [1]. > The Apache

Re: [pool] Another source compatibility break in 2.x

2023-07-21 Thread Gary Gregory
1a or 1b seem fine and least intrusive. Gary On Thu, Jul 20, 2023, 20:28 Phil Steitz wrote: > We have a minor source compat break still in 2.x > > The change to have BaseGenericObjectPool implement Autocloseable forced > addition of an abstract close method. Technically, that could break >

Re: [pool] Another source compatibility break in 2.x

2023-07-21 Thread Elliotte Rusty Harold
On Thu, Jul 20, 2023 at 8:27 PM Phil Steitz wrote: > > We have a minor source compat break still in 2.x > > The change to have BaseGenericObjectPool implement Autocloseable forced > addition of an abstract close method. Technically, that could break > subclass implementations that don't