java.library.path fix for MacOS X (7145798) (original) (raw)
Michael Hall mik3hall at gmail.com
Mon Feb 20 17:47:15 PST 2012
- Previous message: java.library.path fix for MacOS X (7145798)
- Next message: java.library.path fix for MacOS X (7145798)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Feb 20, 2012, at 6:30 PM, Mike Swingler wrote:
On Feb 20, 2012, at 12:16 PM, Greg Brown wrote:
Flattening the prefixed keys to the top-level seems reasonable, and more in-line with existing convention. It's a good idea. Cool. If you think the proposed key names make sense, I'll make that change. JVMRuntime, JVMMainClassName, JVMOptions, and JVMArguments sound like good names. It also sounds like there is demand for a JVMClassPath as well (which would logically necessitate a form of macro expansion to be able to reference inside the app bundle). Perhaps if a JVMClassPath were specified, you could turn off the automatic flat-directory scanning, to keep the rules simple and predictable.
+2
- Previous message: java.library.path fix for MacOS X (7145798)
- Next message: java.library.path fix for MacOS X (7145798)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]