you ask but you know it is gradle right ([1])? ;) It is the risk to drive the build descriptors by code, you can get conflicts using conventions not validating themselves in the build script.
[1] https://github.com/openjdk/jfx/blob/master/build.gradle#L1674 Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://rmannibucau.metawerx.net/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/application-development/java-ee-8-high-performance> Le mar. 28 mai 2024 à 16:53, Tamás Cservenák <ta...@cservenak.net> a écrit : > Howdy, > > well, after a quite long investigation we came to several conclusions: > * 3.9.6 and before worked really "by chance", as > * the POM is invalid > > https://repo.maven.apache.org/maven2/org/openjfx/javafx/21.0.3/javafx-21.0.3.pom > > It uses _same profile IDs for conflicting profies_ (as one can expect, > fields having "ID" in their name are supposed to be, well, "identifiers"). > > In fact, am unsure what produced this POM, as Maven cannot even grasp it > (refuses to load it even): > https://gist.github.com/cstamas/27b948306cddabd00105f747e744e2cd > > Thanks > T > > > On Mon, May 27, 2024 at 11:43 PM John Neffenger <j...@status6.com> wrote: > > > Thank you for the quick response, Tamás. > > > > On 5/27/24 11:51 AM, Tamás Cservenák wrote: > > > Can you create a small reproducer, ideally shared on github or similar > > > service? > > > > This "Hello World" JavaFX project illustrates the problem for me: > > > > Hello JavaFX! > > https://github.com/jgneff/hello-javafx > > > > Just clone and build with: > > > > $ git clone https://github.com/jgneff/hello-javafx.git > > $ cd hello-javafx > > $ mvn clean package > > > > Thanks, > > John > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > >
