RFR: 8342576: [macos] AppContentTest still fails after JDK-8341443 for same reason on older macOS versions
Michael Hall
mik3hall at gmail.com
Tue Oct 29 02:01:17 UTC 2024
> On Oct 28, 2024, at 5:40 PM, Alexander Matveev <alexander.matveev at oracle.com> wrote:
>
> Hi Michael,
>
> > They would also, files in the app directory, all be automatically code signed I think wouldn’t they?
> Yes, files under app directory will be signed as well.
>
> Thanks,
> Alexander
Sorry, I was going to leave it at this but did a little more googling out of curiosity.
https://bugs.openjdk.org/browse/JDK-8274717
https://bugs.openjdk.org/browse/JDK-8274346
I am sort of gathering that this might make more sense on other platforms?
Putting files in an application Contents directory doesn’t seem like a sound practice to me.
Are you aware of any actual use cases of this? Maybe someone has a situation where this makes sense on MacOS but I am still not thinking of any.
The app directory provides a way to do usual java resource loading. There is no such normal provision for accessing something off of an Application's Contents directory that I am aware of.
--mac-dmg-content makes perfect sense for dmg’s.
I am not really familiar with package installs maybe it works better there?
For an application —app-image if you wanted to allow additional files I think they would be better off extermal to the application.
Maybe someplace like the ~/Library/Application\ Support directory.
Again maybe I’m missing something and this is commonly used functionality. If so, feel free to ignore this.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/core-libs-dev/attachments/20241028/43159d28/attachment-0001.htm>
More information about the core-libs-dev
mailing list