openjfx / javafx-gradle-plugin

Gradle plugin that makes it easy to work with JavaFX 11+
https://openjfx.io/
BSD 3-Clause "New" or "Revised" License
359 stars 62 forks source link

Updating from 0.0.14 to 0.1.0 breaks working Quarkus Application #166

Open MarceloRuiz opened 8 months ago

MarceloRuiz commented 8 months ago

I have a multi-module Quarkus Application (that uses the jandex plugin to allow bean discovery) that works fine with plugin 0.0.14:

2024-03-17 11:25:50,169 INFO  [io.quarkus] (main) app 0.0.1 on JVM (powered by Quarkus 3.8.2) started in 0.791s. 
2024-03-17 11:25:50,182 INFO  [io.quarkus] (main) Profile prod activated. 
2024-03-17 11:25:50,182 INFO  [io.quarkus] (main) Installed features: [cdi, smallrye-context-propagation]
2024-03-17 11:25:50,185 INFO  [com.fb.app.QuarkusJFXApplication] (main) Application Started: QuarkusJFXApplication
2024-03-17 11:25:50,211 WARN  [javafx] (executor-thread-2) Unsupported JavaFX configuration: classes were loaded from 'unnamed module @3551a94'
2024-03-17 11:25:58,103 INFO  [io.quarkus] (main) app stopped in 0.012s

but when the plugin is updated to version 0.1.0, the build fails with the following error:

Execution failed for task ':app:quarkusAppPartsBuild'.
> There was a failure while executing work items
   > A failure occurred while executing io.quarkus.gradle.tasks.worker.BuildWorker
      > io.quarkus.builder.BuildException: Build failure: Build failed due to errors
            [error]: Build step io.quarkus.arc.deployment.ArcProcessor#registerBeans threw an exception: java.lang.IllegalArgumentException: Producer method return type not found in index: javafx.fxml.FXMLLoader

How can this be solved? I can provide a minimal application in a zip file if needed. Thanks!

nlisker commented 7 months ago

I don't know about that specific error, but 0.1.0 made some big changes and there's a migration guide from 0.0.14 in the README: https://github.com/openjfx/javafx-gradle-plugin#migrating-from-0014-to-010. Maybe that will help.

MarceloRuiz commented 7 months ago

@nlisker Thanks for the link, I was aware of it, but it did not help in my case...