[hibernate-dev] Depending on JAXB / JDK11 compatibility

Christian Beikov christian.beikov at gmail.com
Wed May 2 17:55:57 EDT 2018

I actually think since the bootclasspath has precedence over the user 
classpath, nothing will happen. It's just that there is an additional 
JAR that needs to be downloaded.

If it's an implementation with zero further dependencies, it might 
actually be an ok solution to add the dependency, as users could simply 
exclude the dependency if they like without messing up other transitive 

Mit freundlichen Grüßen,
*Christian Beikov*
Am 02.05.2018 um 23:48 schrieb Guillaume Smet:
> On Wed, May 2, 2018 at 11:40 PM, Christian Beikov 
> <christian.beikov at gmail.com <mailto:christian.beikov at 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

More information about the hibernate-dev mailing list