Danny Althoff

This might have something to do with the way how Gradle is using their daemon. Normally a task does not require any deep interaction, it's for "working"-stuff. As you are...

@Aqluse can you check if adding `--no-daemon` does result in running your application? ``` gradle jfxRun --no-daemon ```

No, as I wrote, just calling it from CLI ``` gradle jfxRun --no-daemon ```

Can you try to set this: ```groovy jfx { verbose = true } ``` There should be more valuable stuff printed out.

This means when having "verbose" being active (which should be the default while developing) and `--no-daemon` being present, this is what you needed to know?

As far as I understood this issue, you wanted to know what happened when calling `jfxRun`. Setting verbose and non-daemon mode does show more information. If you wanted to know...

@Aqluse I've downloaded your project, you can delete it now. When I find something, I will report back to you.

Now you lost me ... you are still using the gradle daemon. The task "jfxRun" is not compatible with the daemon, as that task was never thought of a real...

Currently there is no IDE-support, yes. This plugin was ment for the bundling-process, but I can see a lot of devs using this for more than just bundling. Nevertheless you...

You might need to adjust the order of the projects depending on each other. To avoid some misconfiguration, please use `afterEvaluate { project -> }` as this plugin does change...