Vlad, the issue is not "someone doesn't want it". In fact, for the most part because of our decision to use the JTA contracts in our API "(not) wanting it" is not really an option.
The issue here is the proliferation of JTA jars (maven coords). We have the Geronimo jars, the JBoss/WildFly jars, etc. So the concerns is when someone wants to use one of the jars other than the one we provide transitively. Yes, the result is the same: they still need to exclude the one we provide transitively. I have argued this for ages... I think this is a fundamental missing construct in Maven dependency mappings: the ability to say "remap" all references to a particular spec jar coord to another. Gradle luckily allows users to do that (granted somewhat verbosely), Maven simply does not. On Wed, Jan 6, 2016 at 10:30 AM Vlad Mihalcea <mihalcea.v...@gmail.com> wrote: > Hi, > > Since the Hibernate core relies on the JTA dependency, I think we > shouldn't provide that dependency. > When someone doesn't want it he should explicitly mark that (e.g. Maven > exclude). > This way we can also address the parent issue: > https://hibernate.atlassian.net/browse/HHH-10178 > > Vlad > On Wed, Jan 6, 2016 at 5:12 PM, Steve Ebersole <st...@hibernate.org> > wrote: > >> HHH-10307[1] is another issue we need to get some consensus on. Initially >> we had removed JTA as a transitive dependency, but that is not really >> valid. We need to discuss alternatives and options. >> >> [1] https://hibernate.atlassian.net/browse/HHH-10307 >> > _______________________________________________ >> hibernate-dev mailing list >> hibernate-dev@lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hibernate-dev >> > _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
