Hi all (and Jerome in particular), I recently submitted a patch to enable the addition of a version attribute in each jar resource element declared in the generated JNLP file. I needed this to enable incremental updates when using the JnlpDownloadServlet. I've been getting a better understanding of how these incremental updates work and it looks like a bit more work will be required on the plugin.
First of all, the version number needs to be stripped from the file name used in the href attribute when a version attribute is provided. Second, we need to be able to bundle multiple versions of the same dependency in the zip artifact produced by the plugin. This is to enable a jardiff to be generated for the differences between the version of the jar on the client and the latest version declared in the JNLP. I haven't given this much thought yet, but the first thing that came to mind was that the way a jnlp project currently declares dependencies won't work. Maybe we could use the dependency plugin to collate the required jar files into a working directory from which they can then be signed and compressed. Any thoughts? Cheers, Kevin
