[jira] Issue Comment Edited: (MJARSIGNER-12) It should be possible to save the keystore in one location for multi module projects

["Sven Kirmess (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MJARSIGNER-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=264670#action_264670 ] 

Sven Kirmess edited comment on MJARSIGNER-12 at 4/26/11 8:02 AM:
-----------------------------------------------------------------

I think I had the problem that the plugin added $PWD in front of the URL but I might be wrong. I tried it again and it worked. Thanks for this hint. :)

Of course, that also requires us to run an http server. I've placed the file on the nexus server as artifact and use this URL but that's another URL to maintain in the pom file. I still think that it might be more convenient to upload the keystore in a jar file as maven artifact and reference this artifact, like the assembly plugin.

      was (Author: skirmess):
    I think I had the problem that the plugin added $PWD in front of the URL but I might be wrong. I tried it again and it worked.

Of course, that also requires us to run an http server. I've placed the file on the nexus server as artifact and use this URL but that's another URL to maintain in the pom file. I still think that it might be more convenient to upload the keystore in a jar file as maven artifact and reference this artifact, like the assembly plugin.
  
> It should be possible to save the keystore in one location for multi module projects
> ------------------------------------------------------------------------------------
>
>                 Key: MJARSIGNER-12
>                 URL: http://jira.codehaus.org/browse/MJARSIGNER-12
>             Project: Maven 2.x Jar Signer Plugin
>          Issue Type: New Feature
>            Reporter: Sven Kirmess
>
> We have a multi module maven setup. The problem is that this plugin requires us to have the keystore either in the same location on all machines or in the source code along each and every pom.xml file.
> I would like to have one of the following:
>  - Save the file on one location in Subversion and use something like
>    <keystore>svn://svn.example.com/trunk/keystore</keystore>
>    and the plugin would have to take care to check out the keystore into every project as needed.
> or
>  - Put the keystore into a JAR file and save that JAR file on the Nexus server. Then make the jarsigner plugin depend on this JAR file, download it for every project and extract the keystore from there. This would be like what the assembly plugin can do for its descriptors.
>   http://docs.codehaus.org/display/MAVENUSER/Assembly+Plugin

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira