Hi Sanne, On Mon, Oct 8, 2012 at 3:34 PM, Sanne Grinovero <sa...@hibernate.org> wrote: > I'll leave it to the gradle gurus on the team to say how to fix that, > but I'm surprised that Maven suggests both dependencies, that should > never be the case.
It doesn't include both, of course. But both dependencies are present and exposed. We often have various dependencies with different versions so it's not a real problem. The problem here is that hibernate-entity-manager requires 2 versions of the same dependency. If I exclude it, I have to maintain the version by hand, which I'm not very fond of, especially for such technical dependencies. With Emmanuel's solution, you'll have to release a new version of hibernate-commons-annotations each time you upgrade jboss-logging in hibernate-entity-manager. That's why I thought excluding the jboss-logging dependency coming from hibernate-commons-annotations in hibernate-entity-manager might be a better idea. It's not a critical problem at all but I think it's worth it to have a clean dependency tree for components as widely used as Hibernate. The fact is that if you use the maven-enforcer-plugin with the dependency convergence rule ( http://maven.apache.org/enforcer/enforcer-rules/dependencyConvergence.html ), just adding the hibernate-entity-manager dependency to any project breaks this rule. -- Guillaume _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
