Message Title

Issue Type:	Bug
Affects Versions:	6.0.11.Final
Assignee:	Unassigned
Components:	build
Created:	09/Aug/2018 05:15 AM
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"
Priority:	Critical
Reporter:	Stéphane Nicoll

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

 
                                                                [INFO] +- org.hibernate.validator:hibernate-validator:jar:6.0.11.Final:compile
[INFO] |  +- javax.validation:validation-api:jar:2.0.1.Final:compile
[INFO] |  +- org.jboss.logging:jboss-logging:jar:3.3.2.Final:compile
[INFO] |  +- com.fasterxml:classmate:jar:1.3.4:compile
[INFO] |  \- org.openjfx:javafx.base:jar:11.0.0-SNAPSHOT:compile
[INFO] |     +- org.openjfx:javafx.base:jar:linux:11.0.0-SNAPSHOT:compile
[INFO] |     +- org.openjfx:javafx.base:jar:mac:11.0.0-SNAPSHOT:compile
[INFO] |     \- org.openjfx:javafx.base:jar:win:11.0.0-SNAPSHOT:compile
 
                                                            

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.

Add Comment

Get Jira notifications on your phone! Download the Jira Cloud app for Android or iOS

This message was sent by Atlassian Jira