You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Christian Schulte (JIRA)" <ji...@codehaus.org> on 2011/04/25 06:59:22 UTC

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

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

Christian Schulte commented on MJARSIGNER-12:
---------------------------------------------

Did you try using an URL for the keystore parameter (http://your.keystore.location/your.keystore.resource) ? I think the jarsigner tool already supports keystore URLs.


> 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