My guess: the jarpath allows you to specify the output jar. The input is always the project artifact. Without jarpath it is signed in place.
Tom On 11/17/06, Wim Deblauwe <[EMAIL PROTECTED]> wrote:
2nd try.... 2006/11/15, Wim Deblauwe <[EMAIL PROTECTED]>: > > Hi, > > according to the documentation it should be possible to sign any jar you > like using the jarPath option. I wanted to use this to sign the jar that the > assembly plugin created, but this does not work, the jar plugin still tried > to sign the actual jar produced by the project, not the one produced by the > assembly plugin. > > any ideas what might be wrong or is this a bug? > > regards, > > Wim >
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
