Remove classifier from JavaFX artifacts when publishing to Maven Central

[jperedadnr]

The JavaFX gradle plugin applies the required platform-dependent classifier to any JavaFX module included in a project.

But if this project is being published with the maven plugin, this plugin generates a pom file based on the existing dependencies. Since the JavaFX ones include the classifier, this classifier will go to the pom. In other words, the pom will have a JavaFX dependency with a classifier based on the platform from where it was published.

If later on this library is consumed in a different platform, artifacts for both platforms will be added, causing a possible conflict due to split package.

To avoid this issue, the JavaFX gradle plugin could add a task to remove the classifier in case the maven plugin is used.

[tobiasdiez]

I think for the same reason, Intellj also adds dependencies for all platforms: although I'm on Windows. This is really annoying, as the linux and mac version have to be removed manually after each gradle sync.

[effad]

Any news on this issue? As the maintainer of ValidatorFX I am not able to release a "correct" POM-File of the library at the moment :-(.