Review Request : JDK-8213362 : Could not find libjava.dylib error when initializing JVM via JNI_CreateJavaVM

[Magnus Ihse Bursie]

On 2018-11-05 15:54, Alan Bateman wrote:
>
>
> On 05/11/2018 14:21, Magnus Ihse Bursie wrote:
>> Hi,
>>
>> Fix looks good, but maybe we should have a regression test of 
>> GetJREPath()?
>>
>> /Magnus
> The fix looks okay but I'm puzzled as to how Eclipse is running into 
> this. Do they locate/call libjli/GetJREPath directly or is this 
> happening then it is called indirectly?

Sorry for the necroposting, but I just noticed the following: In 
Info.plist, on MacOS, we actively publish this key-value data:
         <key>CFBundleExecutable</key>
         <string>libjli.dylib</string>

I'm not sure what this really means or how user's are supposed to relate 
to this key, but if JLI is an internal-only library, we should probably 
not publish it like this. Perhaps this is the way that Eclipse get's 
hold of it..?

/Magnus
>
> -Alan