I usually just build and publish the Branch into my local Maven
repository with:
./gradlew publishToMavenLocal -PMAVEN_PUBLISH=true
-PMAVEN_VERSION=custom-selection
Similar to Andy, I have an repository with a lot of JavaFX Code and
Reproducers and I change the version in my pom.xml (defined as property)
from:
<javafx.version>26</javafx.version>
to:
<javafx.version>custom-selection</javafx.version>
Same workflow with a Gradle based Project. And that makes it very easy
and fast to test something with different versions.
Unfortunately, as of now there are no Sources published (for debugging).
Sometimes I also use the way that John mentioned in the past:
Copying the changed class (e.g. TableView) into a same named package
structure (javafx.scene.control) to effectively overwrite the JavaFX class.
This is only possible without a module-info.
-- Marius
Am 09.04.2026 um 07:08 schrieb Christopher Schnick:
Given a small reproducer code snippet that is not part of a test and
not in the jfx repo, what is the quickest way to run this with a
debugger attached with multiple different jfx builds/development
branches to see the difference? I feel like my workflow is not optimal
and would like to hear how others do it
