Skip to content

Conversation

@Stefterv
Copy link
Collaborator

This change will make sure that Processing will scan the $library/library/$native/modules folder within a library folder, fixing the issues with JavaFX not having access to its modules

Closes#1344
Closes#1327

jarHeads = newFile(nativeLibraryPath).list(jarFilter);
if (jarHeads != null){
for (Stringjar : jarHeads){
cp.append(File.pathSeparatorChar);
Copy link
CollaboratorAuthor

@SteftervSteftervNov 25, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since I am in here, I also cleaned up some duplicated code

Copy link
Collaborator

@catilaccatilac left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yay! Thanks so much for your effort on this

@catilaccatilac merged commit d1641a2 into processing:mainNov 26, 2025
10 of 12 checks passed
@SteftervStefterv deleted the fix-javafx-imports branch November 27, 2025 08:01
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

JavaFX modules are not added to the classpath. JavaFX Requires 'code' Folder to Run

2 participants

@Stefterv@catilac