[chore] Modernize codebase with Java improvements - Replace custom null checks with Objects.requireNonNull

[Pankraz76]

Modernize codebase with Java improvements - Replace custom null checks with Objects.requireNonNull

• Modernize codebase with Java improvements #2277
• Modernize codebase with Java improvements - Use modern Java collections API (toList() instead of Collectors.toList()) #2287

[elharo]

I thought we already did this, but I guess not

[Pankraz76]

but I guess not

merge not. It seems that its convention here to to merge immediately so others can review too. Might enable an auto merge after 10 days non rejected.

[Bukama]

Might enable an auto merge after 10 days non rejected.

Not rejected does not mean approved (at least for me) and taken into account how large Maven is, that the Maven team is not a company and the current situation about cyber attacks (including AI generated ones) I don't think auto merges are a good idea.

[michael-o]

Might enable an auto merge after 10 days non rejected.

Not rejected does not mean approved (at least for me) and taken into account how large Maven is, that the Maven team is not a company and the current situation about cyber attacks (including AI generated ones) I don't think auto merges are a good idea.

I am totally against any automerges.

[Pankraz76]

yes, its a security risk not haven taken into account. Thanks for hint.
If its only possible then with min. approval count increased to 2, better 3, this is altho not pleasant.

[Pankraz76]

@olamy any feedback from your side?

If not might consider merge.

Its just renaming of old method to new one, therefore no delta possible, and removal. No risky s&r brute force.