Querydsl in subprojects

[jjustinic (James Justinic)]

@scphantm

The way it works is it bypasses generating *.java and goes directly to *.class. This is awesome.

With what you’ve posted, both the *.java and *.class file are generated into the classes directory and included in the jar / on the classpath.

@scphantm

I have no idea how the rest of it works. You just include that Jpa dependency and some external doodad begins generating them on the compilejava task.

For the curious, doodad = Annotation Processor

@scphantm

The Q*.class files are there, just nothing sees them.

Taking what you have, I added an example entity in the entity project and usage of it in a “project B”, both directly copied and pasted from the querydsl website and everything works as expected (minus the additional, but non-breaking inclusion of the *.java file).

Considering the most basic example project with querydsl extrapolated from your post works, you might be overlooking something impactful that’s not actually querydsl related.