Re: [hibernate-dev] hibernate-commons-annotations dependencies
Hi Guillaume,
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.
As a workaround, if you define an explicit dependency on jboss-logging
in your <dependencyManagement> section you should be able to avoid any
ambiguity.
I always specify dependency versions explicitly in this form (in our
projects using Maven) so that might explain why we never noticed this
problem.
thanks,
Sanne
On 8 October 2012 13:49, Guillaume Smet <guillaume.smet(a)gmail.com> wrote:
Hi,
I don't know what is your policy about the dependency management but,
currently, when you include hibernate-entity-manager in the pom of an
application, it comes with dependencies to 3.1.0.Final and 3.1.0.CR2.
The problem is that hibernate-commons-annotations-4.0.1.Final requires
3.1.0.CR2 of jboss-logging. See:
http://search.maven.org/remotecontent?filepath=org/hibernate/common/hiber...
I was wondering if it was possible to add an exclusion to the
hibernate-entity-manager pom.xml (or the Gradle equivalent) to not
drag the jboss-logging dependency of hibernate-commons-annotations so
that from the outside the dependencies of hibernate-entity-manager are
clean.
Thanks for your feedback.
--
Guillaume
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev