Dear @sf-support, why are you sending that researcher to us (jEdit)? Don't get fooled by the report starting at jedit.org, that is totally pointless. The first action is to click on the SF project link and the vulnerability they report is on the SF pages and has nothing to do with jEdit.
Thank you very much for the quick help, it seems it is working properly again now. This issue can be closed.
Unable to save new files with current master
Hey there, sorry. I already had the proper fix for this locally, just didn't push yet because it was after some other commits that wait for the release of another project. I reordered the commits now and pushed that fix. Renaming and thus also 2-stage-save should work properly again now in current master.
jedit-community information suddenly gone
`ld` does not find the header objects and libraries when they are not relative to the JAR file
With empty classpath process cannot start
The standard classpath wildcard should not get expanded