On the javapacakger (javafxpackager) side of the house we dodge this by not using the symlinked JLI.
The JDK as it is installed installs a symlink to the libjli.dylib in ...app/Contents/MacOS is actually a symlink. I don't know if you copy it if it will still work, it may want to live in ...app/Contents/Home/jre/lib/jli/libjli.dylib. This is referenced in the default info.plist The way we dodge this for the javapackager is we create our own launch native that opens up the libjli from the location deep in the JRE. And we don't ship the symlink. I can confirm that javapackager 8u20 signs and launchers with 10.9.5, but I haven't tried to submit it to the app store since the signing requirements changes. So I don't know how you launch, but the info.plist cannot refer to the symlinked libjli.dylib if it is symlinked, and it may not even be allowed to exist as a symlink in ...app/Contents/MacOS. So if you can remove the symlink before signing that may help. On Sep 18, 2014, at 10:19 AM, Paul Taylor <paul_t...@fastmail.fm> wrote: > Can somebody help me with this please I just updated from OSX 10.9.4 to > 10.9.5, and it looks like I have to change how I sign Java application after > updating because Im now getting this output after signing with > > export > CODESIGN_ALLOCATE="/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/codesign_allocate" > /usr/bin/codesign --sign "Developer ID Application: P Taylor" --force > --deep --verbose /Applications/SongKong.app > > Im getting: > > /Applications/SongKong.app: the main executable or Info.plist must be a > regular file (no symlinks, etc.) > In subcomponent: > /Applications/SongKong.app/Contents/PlugIns/jdk1.8.0_20.jdk > > and verification with > > /usr/bin/codesign --verify --deep --verbose /Applications/SongKong.app > > gives me > > /Applications/SongKong.app: code object is not signed at all > In architecture: x86_64 > > What do I have to change to fix this ? > > Paul >
