Hi,
I've seen a couple of webstart-m-p issues which have to do with signing and unsigning jars. A few examples (there are a lot more): http://jira.codehaus.org/browse/MWEBSTART-127 : unsignAlreadySignedJars sometimes removes manifest information http://jira.codehaus.org/browse/MWEBSTART-132 : Unsigning already signed jars doesn't work when libPath used http://jira.codehaus.org/browse/MWEBSTART-138 : The number of signed artifacts differ from the number of modified artifacts http://jira.codehaus.org/browse/MWEBSTART-144 : Jar Unsigning Does Not Work For over a year there's a maven plugin especially created to do this task, the maven-jarsigner-plugin [1] For this reason all sign-related actions has been removed from the maven-jar-plugin. IMHO I believe we should leave all the signing to this jar. By now it's the most logical place and it's far more improved than the webstart-m-p can offer. I would suggest to close all these signing-related issues and refer to the jarsigner-plugin. A next step would be to remove this feature from the plugin. Any ideas, agreements or disagreements? - Robert [1] http://maven.apache.org/plugins/maven-jarsigner-plugin
