[mojo-dev] [jira] (MWEBSTART-254) Jnlp templates should include version attribute in jnlp element

[Michael Koch (JIRA)]

Title: Message Title

Michael Koch commented on an issue   Re: Jnlp templates should include version attribute in jnlp element Are you sure that it is enough to add a version to the JNLP file? From my experience, you have to change the version of each Jar which is part of your application if you sign with a different key. The reason is that if you use the version download protocol and the Jar versions don't change, Java Web Start may use cached copies of the Jars which are still signed with the old key. An approach we have taken to fix this is to add a "certificate id" string as part of the Jar version. If we change the key, we also change the certificate id, thus forcing the re-download of all Jars. If you think this is the right way to go, I could prepare a patch. Add Comment   Mojo's Webstart Maven Plugin / MWEBSTART-254 Jnlp templates should include version attribute in jnlp element We spent some time trying to figure out why changing a certificate was causing issues with launching a new version of our webstart applications with a warning about resources signed with different certificates. We traced this to the fact that the jnlp descriptors built using the example templates are not versioned. e.g. http://mojo.codehaus.org/webst... This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email