HannesWell opened a new issue, #118: URL: https://github.com/apache/maven-jarsigner/issues/118
### New feature, improvement proposal In some situations it can be convenient to skip a jar if it's already already signed. There is already the option [removeExistingSignatures](https://maven.apache.org/plugins/maven-jarsigner-plugin/sign-mojo.html#removeExistingSignatures). To generalize this it could be suitable to allow a user to specify a strategy how to deal with existing signatures. For example: - REPLACE (equal to `removeExistingSignature=true`). - RESIGN (equal to `removeExistingSignature=false`). - SKIP - FAIL - ... whatever else is suitable If you think this proposal is useful, I can work on a fix. This is inspired by the `eclipse-jarsigner-plugin`: https://github.com/eclipse-cbi/org.eclipse.cbi/blob/bd01b9668f04cb57b8aa39c18facccd452618443/maven-plugins/eclipse-jarsigner-plugin/src/main/java/org/eclipse/cbi/maven/plugins/jarsigner/JarResigner.java#L47-L54 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
