commons-io VS commons-collections

As you can see in the source code TailerListenerAdapter does nothing if you don't overwrite its methods with your own extending class.

+ Will usually be actively maintained (for example, https://github.com/apache/commons-io has 70 contributors and 360k users).

It should be noted that BidiMap is really just bundling two Maps (though there are multiple implementations).

I've noticed when you look into a lot of classes in some libraries like guava, apache commons, or ReactFX, you'll notice a sort of abstraction pattern. There'll be a class that houses a bunch of common methods. Inside of those methods, instead of putting the relevant logic inside of the method, they'll call an operation-specific class that executes the logic. An example would be PredicateUtils or EventStream. Is there name for this pattern? It doesn't quite seem like it fits the command or service layer patterns.