Using Hibernate Validator with Java 11 brings JavaFX on the classpath

Description

Due to this profile activation, adding Hibernate validator to a Java11 project brings JavaFX on the classpath

I have no idea whether that's a bug or a feature of Maven but, regardless, published pom should ideally be cleared of those build-specific details. For instance, the repository definition is also a problem as that brings oss.sonatype.org to any project that defines Hibernate Validator as a dependency.

Environment

Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 2018-06-17T20:33:14+02:00) Maven home: /Users/snicoll/tools/maven Java version: 11-ea, vendor: Oracle Corporation, runtime: /Library/Java/JavaVirtualMachines/jdk-11.jdk/Contents/Home Default locale: en_BE, platform encoding: UTF-8 OS name: "mac os x", version: "10.13.6", arch: "x86_64", family: "mac"

Activity

Show:

Stéphane Nicoll August 13, 2018 at 3:01 PM

Sweet, thanks a lot for the super fast turnaround!

Guillaume Smet August 13, 2018 at 2:04 PM

the issue is fixed in 6.0.12.Final, already available on Central.

Guillaume Smet August 10, 2018 at 1:21 PM

Yes, I noticed yesterday it's what JavaFX uses to have architecture-dependent dependencies.

Stéphane Nicoll August 10, 2018 at 6:50 AM

That's not what I'd have expected either, but that's a confirmed feature.

Gunnar Morling August 9, 2018 at 10:00 PM

Hum, that's weird, such profile shouldn't be enabled when adding a HV as a dependency (unless things have changed in Maven recently). I could only see it happen when using HV as a parent POM. In any case not what I'd have expected.