You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tony Chemit (JIRA)" <ji...@codehaus.org> on 2013/11/13 22:47:20 UTC

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

     [ https://jira.codehaus.org/browse/MJARSIGNER-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tony Chemit closed MJARSIGNER-12.
---------------------------------

       Resolution: Won't Fix
    Fix Version/s: 1.3
         Assignee: Tony Chemit

I just check and it works well with a url. So then nothing more to be done here.
                
> It should be possible to save the keystore in one location for multi module projects
> ------------------------------------------------------------------------------------
>
>                 Key: MJARSIGNER-12
>                 URL: https://jira.codehaus.org/browse/MJARSIGNER-12
>             Project: Maven Jar Signer Plugin
>          Issue Type: New Feature
>            Reporter: Sven Kirmess
>            Assignee: Tony Chemit
>             Fix For: 1.3
>
>
> 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, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira