@alshain The build seems to be broken by this change, could you please double check locally?

Thanks for the near instant reply @sdeleuze . Unfortuntely, our corporate proxy setup would have me chnage everything to our Nexus, that seems infeasible.

I've taken a guess at the needed local nullability annotations. Could you trigger the build again?

I am running another build on the CI to check.

All commits must include a Signed-off-by trailer at the end of each commit message, see https://github.com/spring-projects/spring-framework/blob/main/CONTRIBUTING.md#submit-a-pull-request for more details. Maybe squash the 2 commits to a single one with the required trailer and force-push?

Still broken, I think you should find a way to run the test locally.

@sdeleuze I'll try to do it at home, there it should be no problem.

I am currently merging various PRs, so don't bother, I will take it from there and refine.

Also note that I will modify your contribution to use List<? extends @Nullable Object[]> in order to allow both nullable and non-nullable elements in the generic type. I think this is the first time we have a use case for a list of array, but I think that applies there. I will add a Kotlin test case to double check it works as expected.