This is probably not much of an issue for most Processing users, but in my workflow I sometimes need to package a runnable application for use on MacOS. I'm on Windows, which doesn't present too much of a problem as I can just use the Mac App skeleton exported by Processing and insert my own JAR files and update the Info.plist file.
There is one recurring problem, however: The JavaApplicationStub files need to have the executable permission flag set for the app to run when copied to Mac. If not the application fails to start. This can be remedied on a Mac by using the Terminal utility to go to the "Contents/MacOS" folder of your app and execute "chmod +x *.
But while doing chmod manually is a workable hack, it gets to be a nuisance and a downright problem if no Mac is on hand to do the trick on. To aggravate the issue, the executable flag also disappears whenever these files are handled on a Windows system, say by unzipping the archive to update the JAR files.
Are there any ways to set the executable flag correctly while on a Windows system? I know the flag is maintained correctly in ZIP files, could it be set while the files are zipped?