Hi John, maven artifacts are generated when providing the following gradle property: -PMAVEN_PUBLISH=true
For the actual maven publication to maven central, Gluon uses a different parent pom file, which indeed has those duplicate profile id's. We'll provide a fix that will be available from 23-ea+19. As a workaround you can: - fallback to maven 3.9.6 or earlier - manually specify the javafx.platform property, i.e.: mvn -Djavafx.platform=linux compile Kind regards, Joeri Op wo 29 mei 2024 om 04:30 schreef John Neffenger <j...@status6.com>: > It looks as if this issue was reported in 2021, 2022, and 2023. The > difference now is that, as of Maven 3.9.7, the failure occurs > immediately when it tries to download the JavaFX dependencies. > > 2021-12-27 > JDK-8279380: Duplicate profile id in JavaFX maven POM > https://bugs.openjdk.org/browse/JDK-8279380 > > 2022-12-22 > JDK-8299352: Duplicate profile id in JavaFX maven POM > https://bugs.openjdk.org/browse/JDK-8299352 > > 2023-03-24 > JDK-8305167: Duplicate profile ids in generated javafx-19.0.2.1.pom > https://bugs.openjdk.org/browse/JDK-8305167 > > Those three bugs were closed as duplicates of the following: > > 2021-12-23 > JDK-8279327: Maven Assembly Plugin Issues Warnings for JavaFx 17 Onwards > https://bugs.openjdk.org/browse/JDK-8279327 > > Comments in that bug report suggest reporting the issue to the JavaFX > Maven Plugin project, but I'm getting the error, and I don't use that > plugin. I also don't use the Maven Assembly Plugin. > > The Maven developers tell me the error is in the JavaFX parent POM file > itself. Is that published by Gluon? So far I've been unable to produce > the Maven artifacts using tasks in the JavaFX Gradle build file. > > Thanks, > John >
