This can be closed.
This can be closed.
This can be closed.
Logging not substituting variables
Speaking of macOS, do you know what versions you officially support? We used to have issues with Full Disk Access-related things using YAJSW 13.05. This new version you provided me, now that this exception is fixed, didn't seem to have that issue. Did you fix macOS related things since 13.05 that aren't in your release notes by any chance?
Yep, that worked!
Version 13.08 logs that it is version 13.07
Looking at the source, it seems like there is not a way.
Is there a way to circumvent this exception by setting configuration properties?
13.08: UnsatisfiedLinkError on macOS 13.1
Seems to be working correctly in 13.08.
Invalid documentation references to jna.tmpdir
I came here to report this as well.
I tested 13.05 and still had issues with uppercase environment variables in Windows (my original issue)
Zip top-level directory
Hello. Do you have any idea when 13.00 alpha will be the new latest stable version? Thanks!
It seems related to the case of the windows environment variables. All of our ${var}-style variables are lower case in our config file, but it seems like starting with 12.14 I have to make them lower case when I initially set them in the .bat file that sets them (and calls the wrapper), whereas with 12.12 I could set them with an upper case name and they would get converted to lower case automatically for use in the config file. Does that make sense with what changes from 12.12 to 12.14? This is...
It seems related to the case of the windows environment variables. All of our ${var}-style variables are lower case in our config file, but it seems like starting with 12.14 I have to make them lower case when I initially set them in the .bat file that sets them (and calls the wrapper), whereas with 12.12 I could set them with an upper case name and they would get converted to lower case automatically for use in the config file. Does that make sense with what changes from 12.12 to 12.14? This is...
I forgot to mention, my expanded paths that aren't working contain ?unresolved?
Environment variable issues on Windows
Good call, that worked. Thanks!
--add-opens JVM arg issue