+1 for listing the API dependency "javax.xml.bind:jaxb-api". Not sure about the implementation though, maybe we can use "com.sun.xml.bind:jaxb-impl" as an optional dependency? Mit freundlichen Grüßen, ------------------------------------------------------------------------ *Christian Beikov* Am 02.05.2018 um 20:38 schrieb Sanne Grinovero: > With JAXB being part of the JDK in Java 8, Hibernate ORM doesn't list > it as a runtime dependency. > > Java 9 users have been suggested to use the JVM option "--add-modules > java.xml.bind" to avoid the JVM hiding the JAXB library from > classpath. > > With Java 11 the java.xml.bind is no longer available; what should we > suggest to users? > > Should we list it as an explicit dependency in the released pom files? > > Thanks, > Sanne > _______________________________________________ > hibernate-dev mailing list > hibernate-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev _______________________________________________ hibernate-dev mailing list hibernate-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

+1 for listing the API dependency "javax.xml.bind:jaxb-api". Not sure about the implementation though, maybe we can use "com.sun.xml.bind:jaxb-impl" as an optional dependency?

Mit freundlichen Grüßen, ------------------------------------------------------------------------ *Christian Beikov* Am 02.05.2018 um 20:38 schrieb Sanne Grinovero: > With JAXB being part of the JDK in Java 8, Hibernate ORM doesn't list > it as a runtime dependency. > > Java 9 users have been suggested to use the JVM option "--add-modules > java.xml.bind" to avoid the JVM hiding the JAXB library from > classpath. > > With Java 11 the java.xml.bind is no longer available; what should we > suggest to users? > > Should we list it as an explicit dependency in the released pom files? > > Thanks, > Sanne > _______________________________________________ > hibernate-dev mailing list > hibernate-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev _______________________________________________ hibernate-dev mailing list hibernate-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

Hi Sanne, On Wed, May 2, 2018 at 11:24 PM, Sanne Grinovero <sanne(a)hibernate.org&gt; wrote: > > <!-- All replacements for JAXB --> > <dependency> > <groupId>javax.xml.bind</groupId> > <artifactId>jaxb-api</artifactId> > <scope>provided</scope> > </dependency> > > <dependency> > <groupId>com.sun.xml.bind</groupId> > <artifactId>jaxb-impl</artifactId> > <scope>test</scope> > </dependency> Not sure where you got these dependencies. I think the one we should use is the following: <groupId>org.glassfish.jaxb</groupId> <artifactId>jaxb-runtime</artifactId> (which comes with quite a few transitive dependencies unfortunately)

JAXB is currently maintained here: https://javaee.github.io/jaxb-v2/.

HTH -- Guillaume

On 2 May 2018 at 21:30, Christian Beikov <christian.beikov(a)gmail.com&gt; wrote: > +1 for listing the API dependency "javax.xml.bind:jaxb-api". Not sure > about the implementation though, maybe we can use > "com.sun.xml.bind:jaxb-impl" as an optional dependency? Hi Christian, right that's what makes it confusing. We might want to list the jaxb-api explicitly but it's not enough to make it work: people will need to know to list several more dependencies. This is what I've been experimenting with in the Search testsuite (which uses Hibernate ORM): <!-- All replacements for JAXB --> <dependency> <groupId>javax.xml.bind</groupId> <artifactId>jaxb-api</artifactId> <scope>provided</scope> </dependency> <dependency> <groupId>com.sun.xml.bind</groupId> <artifactId>jaxb-impl</artifactId> <scope>test</scope> </dependency> <dependency> <groupId>com.sun.xml.bind</groupId> <artifactId>jaxb-core</artifactId> <scope>test</scope> </dependency> <dependency> <groupId>javax.activation</groupId> <artifactId>javax.activation-api</artifactId> <scope>provided</scope> </dependency> I'm afraid that we might as well not list jaxb-api as users need to understand this all either way. Thanks, Sanne > > Mit freundlichen Grüßen, > ------------------------------------------------------------------------ > *Christian Beikov* > Am 02.05.2018 um 20:38 schrieb Sanne Grinovero: >> With JAXB being part of the JDK in Java 8, Hibernate ORM doesn't list >> it as a runtime dependency. >> >> Java 9 users have been suggested to use the JVM option "--add-modules >> java.xml.bind" to avoid the JVM hiding the JAXB library from >> classpath. >> >> With Java 11 the java.xml.bind is no longer available; what should we >> suggest to users? >> >> Should we list it as an explicit dependency in the released pom files? >> >> Thanks, >> Sanne >> _______________________________________________ >> hibernate-dev mailing list >> hibernate-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hibernate-dev > _______________________________________________ > hibernate-dev mailing list > hibernate-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev

On Wed, May 2, 2018 at 11:40 PM, Christian Beikov <christian.beikov(a)gmail.com <mailto:christian.beikov@gmail.com>> wrote: People will have to adapt to this and add their own JAXB implementation, just like they now use Hibernate as JPA implementation. What happens if we add a strong dependency to a JAXB implementation in addition to the one from the JDK (8)? -- Guillaume