"Because signing certificates typically expire annually, this caused customers significant problems by forcing them to re-sign deployed JAR files annually."
the question is: do you have to provide a (new) valid eclipse plugin update site? or do I have to inspect and check the IWSVA for outdated routines of checking Java artifacts?
Where is the expiration coming from? I see that jar was uploaded 8 juli. As a workaround, you can always download the zip and install manually (see http://activiti.org/designer/archived/).
My guess is that the expiration relates to the certificate in the "META-INF" directory of the JARs (see here). The modification date of the certificates under directory META-INF from this JAR are September 2013.