'lo there Sébastien.
I have found that you will sign the jalviewLite applet in version 2.8.1
When do you plan to release it?
I'm currently waiting on a request for a certificate from CERTUM - who provide free certificates for OSS software (I hope!). I'll then release a signed version of 2.8b1 - which will be the last in the 2.8.0 series as soon as I receive it.
The recent Java updates, and more complex Apple code signing requirements have kept me busy - Jalview now has an official Apple ID, and I'm trying to integrate the codesign step into our release process for the Jalview installer.
Also I have tried to sign the jalview version we modified for MyHits
(version 2.4+) by signing it with our own certificate.
No problem to sign it but when I want to run it it displays a warning
message, only after clicking on the launch button, saying that I try to
run a mix of signed and unsigned classes.
Do you know what could cause this?
this is due to a couple of issues -
the original jalview build script didn't create an index file - and so when the jarsigner operated on it, it didn't actually sign the index file, but created one after it was done. I've fixed the builder so JalviewLite will run without that warning. You can try it out in the 'latest build of the current release branch'.
There are a couple of other wrinkles, however:
* If you link JmolApplet with Jalview, that needs to be fully signed in the same way (with the index created before hand) (again, this is fixed in the build system now)
I'll most likely post an article on the website about all this, since getting all this right is pretty tricky - particularly for someone new to Java development. I'll also be updating the source building instructions to allow for specifying deployment URLs, etc.
On 15/11/2013 15:01, Moretti Sébastien wrote: