Update documentation to use `jakarta.persistence.*` for Querydsl setup

[weaselmetal]

Hi,

I tried to follow these instructions https://docs.spring.io/spring-graphql/reference/data.html#data.querydsl.build but even with querydsl 5.1.0 I had no success. I think I would have to go back to javax.persistence.Entity (and other javax stuff) but that feels wrong with Spring Boot 3.4.0.

With

mvn clean compile -X -Dprocessor=com.querydsl.apt.jpa.JPAAnnotationProcessor

and

<plugin>
	<groupId>org.apache.maven.plugins</groupId>
	<artifactId>maven-compiler-plugin</artifactId>
	<version>3.13.0</version>
	<configuration>
		<source>21</source>
		<target>21</target>
		<annotationProcessorPaths>
			<path>
				<groupId>com.querydsl</groupId>
				<artifactId>querydsl-apt</artifactId>
				<version>5.1.0</version>
			</path>
		</annotationProcessorPaths>
		<generatedSourcesDirectory>${project.build.directory}/generated-sources/annotations
		</generatedSourcesDirectory>
		<compilerArgs>
			<arg>-proc:only</arg>
		</compilerArgs>
	</configuration>
</plugin>

I'm warned that

[WARNING] Annotation processing without compilation requested but no processors were found.

Ultimately, no Q... classes are generated. Let me know if I'm doing something wrong, but the Spring Boot version 3.4 with its graphql-starter doesn't work with repository that extends QuerydslPredicateExecutor.

[mp911de]

Make sure to use the jakarta classifier for all Querydsl artifacts, including the annotation processor querydsl-apt. Querydsl provides artifacts with the jakarta classifier for transition from javax to jakarta.

[weaselmetal]

Thanks for the response @mp911de! Since I wasn't willing to accept my failure, I spent some time on research, which led me to this article https://www.patrick-gotthard.de/querydsl-mit-spring-boot-3-nutzen/ (in the end).
Ultimately I created this little project: https://github.com/weaselmetal/qdsltest
So yes, once you know how (I did not know about the jakarta classifier) it is possible to use QueryDSL in Spring Boot 3.x.

Perhaps the Spring page I referenced in my OP should be updated, but you labelled this issue accordingly already. Thanks again Mark!

[mp911de]

The issue comes from us using javax annotations in Spring GraphQL 1.0.x and not updating the docs with the migration to Jakarta Annotations/Spring Boot 3.