My idea was to use those artifacts to write a custom maven repository /
artifact resolver which will just download those artifacts directly from
the GitHub actions runs and serve them to build scripts as normal maven
dependencies. I would have to look into the details for that, but that
should work somehow. That way, you could skip the local build step when
testing the PRs of others, i.e. when you don't need to make changes to
the jfx source.
On 15/09/2026 12:10, Marius Hanl wrote:
The idea is interesting.
At least for me, I'm not sure it is faster than my current workflow.
I'm usually checking the branch out and building+publishing it with
Gradle.
And as I usually test the changes with multiple applications, I just
need to change the JavaFX version in the pom.xml or build.gradle.
Most of the time it is already set locally.
What would your workflow look like?
-- Marius
Am 09.09.2026 um 22:41 schrieb Christopher Schnick:
I just thought that since the GitHub workflows for any jfx repo PR
build and test the repository, would it be possible to build and
upload the .jars and .jmods to the PR workflow as well? That would
make it easier for some people to run applications to test those PRs
with the dependencies.
