MAS codesign requirements break Java app signing

[Danno Ferrin]

When packaging hte JRE for javapackger, we remove a lot of stuff.  One of those is the symbolic link in .../Contents/MacOS/libjli.dylib.  That would explain why files=6 as opposed to files=7


On Nov 10, 2014, at 6:13 PM, Zach Oakes <zsoakes at gmail.com> wrote:

> I actually get a similar result when I run "codesign -dv" on the app bundle
> created by javapackager, except it says files=6. As far as your other
> command, I get this when I run it on the one created by appbundler:
> 
> MyApp.app/: valid on disk
> MyApp.app/: satisfies its Designated Requirement
> 
> On Mon, Nov 10, 2014 at 8:03 PM, Michael Hall <mik3hall at gmail.com> wrote:
> 
>> On Nov 10, 2014, at 6:46 PM, Zach Oakes <zsoakes at gmail.com> wrote:
>> 
>> Sealed Resources version=2 rules=12 files=7
>> 
>> 
>> The files=7 still seems strange.
>> 
>> I re-read the Mavericks part of the earlier mentioned TN. Still not
>> entirely clear on the resource envelope thing though.
>> 
>> From farther in the TN this is supposed to be a "Gatekeeper"-like
>> verification
>> codesign --verify --deep --verbose=2 Foo.app
>> does it show any problems?
>> 
>> You can manually tweak Info.plist's for testing, or as a matter of habit
>> for me, pre-signed tweaks of course. Developer tools I think pops up it's
>> own application or you can text edit it as plain xml.
>> 
>> Michael Hall
>> 
>> *trz *nio.2 for OS X http://www195.pair.com/mik3hall/index.html#trz
>> 
>> *HalfPipe *Java 6/7 shell app
>> http://www195.pair.com/mik3hall/index.html#halfpipe
>> 
>> *AppConverter *convert Apple jvm to openjdk apps
>> http://www195.pair.com/mik3hall/index.html#appconverter
>> 
>> 
>> 
>> 
>> 
>>