Hi there!
We are (finally) in the process of converting a project to
commons-collections4. Unfortunately, we have a few APIs that return
commons-collections3's Predicates.
CC4 deprecates the custom Predicate class (good!), and these just extend
JDK Predicates
(https://commons.apache.org/proper/c
We don't want to break binary compatibility within the 4.x release line.
Gary
On Mon, Jul 1, 2024, 12:26 PM Julian Reschke
wrote:
> Hi there!
>
> We are (finally) in the process of converting a project to
> commons-collections4. Unfortunately, we have a few APIs that return
> commons-collection
you are correct. it was using some older transitive deps.. resolved. thank you
for your patience .
Sent: Sunday, July 07, 2024 at 11:12 AM
From: "Gary Gregory"
To: julian.resc...@gmx.de.invalid
Cc: "Commons Developers List"
Subject: Re: [collections] Predicate vs Pre
On 07.07.2024 17:12, Gary Gregory wrote:
We don't want to break binary compatibility within the 4.x release line.
Gary
...
Would we have to?
Best regards, Julian
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
F
On 08.07.2024 11:18, Julian Reschke wrote:
On 07.07.2024 17:12, Gary Gregory wrote:
We don't want to break binary compatibility within the 4.x release line.
Gary
...
Would we have to?
OK, so this is about the return values.
It's still unfortunate, because it makes it harder to convert exis
Hello Juilan,
I think this should be a driver for Collections 5 because:
- we don't want to break BC
- what would start with copy pasta for one class could degenerate into a
ton of it
WDYT?
Gary
On Mon, Jul 8, 2024, 6:21 AM Julian Reschke
wrote:
> On 08.07.2024 11:18, Julian Reschke wrote:
>
