Hi Sebastien.. On 15/11/2013 16:26, Moretti Sébastien wrote: > Could the signed/unsigned warning come from non-class files in our > jar? .build_properties images/idwidth.gif images/link.gif you can check whether all content is signed using the jarsigner -verbose -verify <jar>
>> You should add the following lines to the manifest of every jar file, before >> signing with the certificate. >> >> Codebase: *.my.domain.com >> Caller-Allowable-Codebase: *.my.domain.com >> Permissions: all-permissions > Will try to follow that. I think Andrew will be guest author on the blog - he's gone through this particular pain before, and that was with far less crazy java restrictions ;) Please let us know how you get on - I've been experimenting with the above fields and have found that things were not behaving as I expected on all systems! Jim. _______________________________________________ Jalview-discuss mailing list [email protected] http://www.compbio.dundee.ac.uk/mailman/listinfo/jalview-discuss
