A DESCRIPTION OF THE PROBLEM :
This is a followup to bug JDK-8279380 (Duplicate profile id in JavaFX maven POM) [1]. The problem is that the just released Eclipse (2024-06) IDE ships with maven 3.9.7 that triggers that bug. The effect is that no projects with use OpenJFX can be built in eclipse.

Maven already fixed the behavior in version 3.9.8 [2]. The thing is, they should not need to - the root cause always was a broken pom in OpenJFX. Actually, I would like stronger enforcing of "proper" poms, but I digress.

There should be a backports of the fix, as a backport should be really easy as only a couple of ids in the affected pom need to change (I did that locally and verified that it would fix the build issues with maven/eclipse).
The only version with a fix is 23-EA and GA is not released until September. Also, there are LTS versions (17 and 21) that should IMHO get those fixes (I hope I interpreted that right - the OpenJFX homepage links to gluonhq for downloads and there versions 17 and 21 are marked as LTS). Because that is the whole reason LTS exists, right?

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Build any maven project with JFX as dependency with maven version 3.9.7.
Or simply look at the pom.xml of org.openjfx:javafx (checked with version 17.0.11, 19, 21, 21.0.3). All profile ids are duplicated).



CUSTOMER SUBMITTED WORKAROUND :
Downgrade eclipse or patch maven artifacts in eclipse. Upgrade OpenJFX to 23-EA.

FREQUENCY : always