Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
JPA API should be an optional dependency #654
The JPA module of Querydsl currently depends on the Hibernate provided JPA 2.0 API JAR in compile scope. Unfortunately this creates conflicts when you're using a Hibernate version that pulls in the JPA 2.1 JAR as the API JARs have the JPA version in their artifact names which prevents Maven's conflict resolution mechanism from working correctly. So you'll end up with both JARs on the classpath and the persistence provider potentially failing, depending on the order of them.
So I think it'd be better to make the API JAR an optional or provided dependency as it will be pulled in by the persistence provider anyway.