I added a profile in the pom.xml of my project (see production profile in petclinic-standalone), to generate a Webstart-version of my client and sign it with my own certificate. Currently it's impossible to start the client via Webstart, as one jar (bcprov-jdk15-133.jar) is signed with a different certificate.
I just grepped through the buildlog and discovered, that the jar is skipped and does actually no get signed with my certificate, as it's already signed with a certificate of the vendor/provider:
Has anyone some experience on how to modify the pom.xml to sign all dependent jars, regardless of them being already signed or not?
[debug] jarsigner executable=[c:\Programme\Java\jdk1.6.0_01\jre\..\bin\jarsigner.exe]
[debug] Executing: c:\Programme\Java\jdk1.6.0_01\jre\..\bin\jarsigner.exe -verify c:\dev\workspace\rcp-client\target\jnlp\bcprov-jdk15-133.jar
[info] jar verified.
[info] JAR c:\dev\workspace\rcp-client\target\jnlp\bcprov-jdk15-133.jar is already signed. Skipping.
Thanks in advance for any advice,