deprecated ObjectUtils defaultIfNull in favor or getIfNull overload getFirstNonNull with collection support

[Pankraz76]

Thanks for your contribution to Apache Commons! Your help is appreciated!

Before you push a pull request, review this list:

• Read the contribution guidelines for this project.
• Run a successful build using the default Maven goal with mvn; that's mvn on the command line by itself.
• Write unit tests that match behavioral changes, where the tests fail if the changes to the runtime are not applied. This may not always be possible but is a best-practice.
• Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• Each commit in the pull request should have a meaningful subject line and body. Note that commits might be squashed by a maintainer on merge.

[Pankraz76]

is this any good?

[garydgregory]

Hello @Pankraz76

There are conflicts in the PR so I brought this in slightly differently in git master. You are credited in the commit comment and changes.xml

TY!

[Pankraz76]

thx.

[brettkail-wk]

Out of curiosity, why is this rename/deprecation useful? Subjectively, defaultIfNull seems clearer than getIfNull, particularly when statically imported.

[Pankraz76]

The TODO directive given, it's considered deprecated to avoid breaking change.

I like both approaches, but the default context is somewhat implied. While having a verbose API is nice for beginners, for those used to it, this feels like overhead.

Since it's either/or, why do we need to explicitly mention the default? Asking this question could argue why not renaming to returnEtherValueOrDefaultValueIfNull this is a very verbose version giving good testament on naming.

considering:

big scope -> small name

small scope -> big name