return List instead of Iterable and adapt to new interface-hierarchy

[fladdimir]

proposal for resolving #201

[reda-alaoui]

Hi @fladdimir ,
Sorry for the time it took me to take a look. I am ok with your changes but we need to have a migration window.

Would it be possible to not touch the current repository interfaces, and create new ones in a new repository2 package?

I want people to migrate incrementally if needed, by exposing 2 repository trees (the deprecated one and yours), until the next Spring major version.

[reda-alaoui]

.

[fladdimir]

Hi @reda-alaoui, Thank you for the feedback!
I fully understand that the major version numbers should be kept in sync and thus a breaking change is not possible at the moment.
As the proposed change does not provide much functionality, it is probably not worth to introduce a whole new repository(2) interface tree / package?
As long as nothing more important/useful comes up, it might just be simpler to wait for the next spring-data-jpa major release?