Quarkus: Quarkus extension for spring data API - automatic repository implementation generation

[TMBD]

Hello,

I am trying to migrate a spring project in quarkus and I am using quarkus extension for spring data API.

As they said in the quarkus doc : Interfaces that extend org.springframework.data.repository.Repository are automatically implemented and the generated repositories are also registered as beans so they can be injected into any other bean (source : https://quarkus.io/guides/spring-data-jpa#what-is-supported). But in the spring doc they said that instead of extending org.springframework.data.repository.Repository we can alternatively annotate our interface with @RepositoryDefinition and it will cause the same behaviour as extending org.springframework.data.repository.Repository (source : https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repositories.definition-tuning).

My question is : Does spring data API generate automatically the repository that is annotated with @RepositoryDefinition since it has the same behavior as extending org.springframework.data.repository.Repository ?
If no, is there any other way to make spring data API generate the repository that is annotated with @RepositoryDefinition ?

Note that I can't modify the package where the interface is declared since it is a third party library.

Thanks in advance

[quarkusbot]

/cc @geoand

[geoand]

Thanks for reporting!

@RepositoryDefinition isn't supported at the moment, but I don't see why we can't support it. I'll look into next week.

[TMBD]

Thank's @geoand for your response.

It will really help me if you can implement it because I haven't found another alternative.
What can I do to follow it and be informed when it is supported ?

Also tell me if I have to close the issue or wait until the problem is solved...

[geoand]

I'll post an update here when I have one, so just keep an eye out for this issue

[geoand]

I'm on PTO, but I took at look at @RepositoryDefinition and as I expected this is really easy for us to implement. I'll fix it soon and hopefully we can have it for 1.6.1.Final

[geoand]

10629 takes care of this

[TMBD]

Ok @geoand. I'll follow it.