Thanks Wayne. Got some initial idea. -----Original Message----- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Friday, April 07, 2006 10:59 AM To: Maven Users List Subject: Re: KEYSTORES in M2 : is it possible to create / use KEYSTORE in M2 ?
Ah, in that case, you are probably going to want to take a look at the following email thread: From: Mark Hewett <[EMAIL PROTECTED]> To: Maven Users List <users@maven.apache.org> Date: Mar 30, 2006 6:43 PM Subject: Re: [M2] How to sign a jar file Mark included his pom.xml which includes specifics for how his group is signing jars etc. Wayne On 4/6/06, Sharma, Jaikumar <[EMAIL PROTECTED]> wrote: > As you know, keystores can be created and manipulated using keytool in > Java, which is used to store / verify the credentials etc in keystore. > Use case I am thinking about is singing a jar using keystore stored > entries. Regards, > Jaikumar > > -----Original Message----- > From: Wayne Fay [mailto:[EMAIL PROTECTED] > Sent: Thursday, April 06, 2006 10:35 PM > To: Maven Users List > Subject: Re: KEYSTORES in M2 : is it possible to create / use KEYSTORE > in M2 ? > > > Keystore for... what exactly? What's the use case/what are you trying > to do exactly? > > Wayne > > > On 4/6/06, Sharma, Jaikumar <[EMAIL PROTECTED]> wrote: > > Dear. > > Is it possible to create / use keystores in M2 ? > > Regards. > > - - - - - - - DISCLAIMER- - - - - - - - > > Unless indicated otherwise, the information contained in this > > message is privileged and confidential, and is intended only for the > > use of the > > addressee(s) named above and others who have been specifically > authorized to > > receive it. If you are not the intended recipient, you are hereby > notified > > that any dissemination, distribution or copying of this message > > and/or attachments is strictly prohibited. The company accepts no > > liability > for any > > damage caused by any virus transmitted by this email. Furthermore, > > the company does not warrant a proper and complete transmission of > > this information, nor does it accept liability for any delays. If > > you have received this message in error, please contact the sender > > and delete > the > > message. Thank you. > > > > > - - - - - - - DISCLAIMER- - - - - - - - > Unless indicated otherwise, the information contained in this message > is privileged and confidential, and is intended only for the use of > the > addressee(s) named above and others who have been specifically authorized to > receive it. If you are not the intended recipient, you are hereby notified > that any dissemination, distribution or copying of this message and/or > attachments is strictly prohibited. The company accepts no liability for any > damage caused by any virus transmitted by this email. Furthermore, the > company does not warrant a proper and complete transmission of this > information, nor does it accept liablility for any delays. If you have > received this message in error, please contact the sender and delete the > message. Thank you. > > - - - - - - - DISCLAIMER- - - - - - - - Unless indicated otherwise, the information contained in this message is privileged and confidential, and is intended only for the use of the addressee(s) named above and others who have been specifically authorized to receive it. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message and/or attachments is strictly prohibited. The company accepts no liability for any damage caused by any virus transmitted by this email. Furthermore, the company does not warrant a proper and complete transmission of this information, nor does it accept liability for any delays. If you have received this message in error, please contact the sender and delete the message. Thank you.