|
Hi there,
Thanks for the great plugin, we have been using it for many projects. But we faced with one issue recently. The problem is the following.
In our client application we use some thirdparty jars (httpcliet, log4j, etc.) along with our own jars. When we updating our jars we increment their versions and our users get the updates of the changed files.
Everything is fine until we update the certificate, that is used for signing the jars. Javaws cannot run our application, error: 'jar resources in jnlp are not signed by the same certificate'.
I have tried to find an existing solution for this issue, but without success. We need some way to force the update of the changed files, even if their actual version (${project.version}) is remaining the same. This can be done in two ways:
1. Deleting application to the client side; or
2. Changing the version attribute in jnlp file.
The first way is not appropriate for us, because we think this should be done automatically, without forcing the user to delete something. Thus we have to choose the second way. So, I plan to provide a patch with the following solution.
We may add additional config parameter, say, versionSuffix that will be added to the verion attribute in the generated jnlp file and in the version.xml. For example:
<configuration>
<versionSuffix>-20121121</versionSuffix>
<configuration>
<resources>
<jar href="" class="code-quote">"lib/log4j.jar" version="1.2.16-20121121"/>
</resources>
<resource>
<pattern>
<name>log4j.jar</name>
<version-id>1.2.16-20121121</version-id>
</pattern>
<file>log4j-1.2.16.jar</file>
</resource>
I would like to hear what do you think of it.
Thanks in advance.
– Viktor
|
