Hi, we had some requirements that are not yet covered by the webstart-maven-plugin. Unfortunately I had to apply them quite fast, so I applied the changes to the code and we have an own version of the plugin now.
The main requirements were the following: 1. Be able to supply the download=„progress“ attribute to a dependency in the plugin configuration. The solution we used is quite straight forward and not very robust. We simply add a new parameter „download“ to the jarResource configuration part. 2. Apply a workaround for a Java Web Start Issue. This is an issue that first came up with 7u45. There was a security warning about a missing permissions attribute in a manifest although all jar manifest files were absolutely correct. This was also added to the known bugs in 7u45. Unfortunately Oracle did not fix with 7u51. I found a discussion here https://community.oracle.com/thread/2594060?start=0&tstart=0 with a workaround. It basically consists of two parts. One has to add one jar file that is not versioned (feature already available in plugin) and you have to remove the main=„true“ from all jars in the jnlp file. The second thing was not possible with the plugin. One jar has to be the main one. I checked the JNLP specification and found no place where this main=„true“ attribute was said to be mandatory, so we removed that code. The main class can also be applied to the application-desc tag. I would be very happy if there is a way to bring these changes to the webstart-maven-plugin, so that we do not have to maintain an own version. With this email I would like to ask about any requirements concerning those changes (tests for example) and maybe how I can contribute the changes that we did. Best regards André
