Mark,

I tried your suggestion first since I had already attempted that one once.
It worked perfectly!  What I was overlooking was how to get the
2.1-SNAPSHOTversion into my repository.

Thanks again!
TJ

On 3/30/06, Mark Hewett <[EMAIL PROTECTED]> wrote:
>
> We are using the following.
>
> <plugin>
>   <artifactId>maven-jar-plugin</artifactId>
>   <executions>
>     <execution>
>       <goals>
>         <goal>sign</goal>
>       </goals>
>     </execution>
>   </executions>
>   <configuration>
>     <jarpath>${project.build.directory}/${project.build.finalName
> }.jar</jarpath>
>     <signedjar>${ project.build.directory}/signed/${
> project.build.finalName}.jar</signedjar>
>     <keystore>${keystore.location}</keystore>
>     <storepass>${keystore.storepass}</storepass>
>     <keypass>${ keystore.keypass}</keypass>
>     <alias>${keystore.alias}</alias>
>   </configuration>
> </plugin>
>
> The keystore properties are defined in our parent POM, but you can
> just hard code them
>
> You will also need to enable snapshots, since this needs the
> 2.1-SNAPSHOT version of the maven-jar-plugin. See
> http://maven.apache.org/guides/development/guide-testing-development-plugins.html
> .
>
> This also seems to install the signed JAR into the repository, in
> place of the unsigned JAR.
>
> Hope this helps.
> Mark
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Reply via email to