Hi Jerome, No, never solved to my satisfaction. Right now I just dump the certificate onto a known location on the build server. Nice to know that there are some possibilities in the air. I like the first suggestion for its simplicity.
/Henrik >-----Original Message----- >From: Jerome Lacoste [mailto:[EMAIL PROTECTED] >Sent: 2. februar 2008 13:05 > >On Oct 25, 2007 11:36 AM, Henrik Dohlmann <[EMAIL PROTECTED]> wrote: >> We have one common keystore with our certified key which we want to >use for a lot of different projects. >> Do you have a suggestion on how to handle that? >> I am hoping that it is possible to drop this keystore in its own >project and depend upon it from other projects, but I am unclear about >how to point to the actual keystore file in that dependant project. >> Can I create a pom-like project with the keystore attached and somehow >point to the keystore-file in the local repository, or can I use some >sort of assembly magic to pull the keystore from its project and point >to that? > >Henrik > >Did you end up solving your problem ? > >I know of 2 potential solutions > >* there's a request in the webstart plugin to give the availability to >use a URI for a keystore. That way the keystore could reside in a jar, >on a remote server etc. Not implemented > >* there's also in the webstart plugin a pluggable API to use a >different sign jars. Some people hide their keystore and password >configuration behind a service and sign their jars using HTTP. The >code is also available somewhere in the webstart mail archives or >Jira. That could be an interesting project to maintain. > >Cheers, >Jerome
