Return-Path: 
 <hama-dev-return-6744-apmail-incubator-hama-dev-archive=incubator.apache.org@incubator.apache.org>
X-Original-To: apmail-incubator-hama-dev-archive@minotaur.apache.org
Delivered-To: apmail-incubator-hama-dev-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 91F3596F8
	for <apmail-incubator-hama-dev-archive@minotaur.apache.org>;
 Thu, 23 Feb 2012 16:51:12 +0000 (UTC)
Received: (qmail 84147 invoked by uid 500); 23 Feb 2012 16:51:12 -0000
Delivered-To: apmail-incubator-hama-dev-archive@incubator.apache.org
Received: (qmail 84104 invoked by uid 500); 23 Feb 2012 16:51:12 -0000
Mailing-List: contact hama-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:hama-dev-help@incubator.apache.org>
List-Unsubscribe: <mailto:hama-dev-unsubscribe@incubator.apache.org>
List-Post: <mailto:hama-dev@incubator.apache.org>
List-Id: <hama-dev.incubator.apache.org>
Reply-To: hama-dev@incubator.apache.org
Delivered-To: mailing list hama-dev@incubator.apache.org
Received: (qmail 84034 invoked by uid 99); 23 Feb 2012 16:51:12 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Feb 2012 16:51:12 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED,T_RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Feb 2012 16:51:09 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id CDC9C336525
	for <hama-dev@incubator.apache.org>; Thu, 23 Feb 2012 16:50:48 +0000 (UTC)
Date: Thu, 23 Feb 2012 16:50:48 +0000 (UTC)
From: "Thomas Jungblut (Issue Comment Edited) (JIRA)" <jira@apache.org>
To: hama-dev@incubator.apache.org
Message-ID: 
 <1246811356.10458.1330015848844.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1246421044.9479.1329999348747.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Issue Comment Edited] (HAMA-514) Add maven-gpg-plugin to
 parent POM file
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org


    [ https://issues.apache.org/jira/browse/HAMA-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13214847#comment-13214847 ] 

Thomas Jungblut edited comment on HAMA-514 at 2/23/12 4:50 PM:
---------------------------------------------------------------

I'm switching this verify to deploy phase rather than to the verify phase. It can cause Jenkins to hang because of default password entry. 
                
      was (Author: thomas.jungblut):
    I'm switching this verify to package phase rather than to the verify phase. It can cause Jenkins to hang because of default password entry. 
                  
> Add maven-gpg-plugin to parent POM file
> ---------------------------------------
>
>                 Key: HAMA-514
>                 URL: https://issues.apache.org/jira/browse/HAMA-514
>             Project: Hama
>          Issue Type: Improvement
>          Components: build 
>    Affects Versions: 0.4.0
>            Reporter: Edward J. Yoon
>            Assignee: Edward J. Yoon
>             Fix For: 0.5.0
>
>         Attachments: gpg-plugin.patch
>
>
> I noticed that 'maven-gpg-plugin' is required to deploy signed artifacts to repository. We need to add this plugin as below.
> {code}
>       <plugin>
>         <groupId>org.apache.maven.plugins</groupId>
>         <artifactId>maven-gpg-plugin</artifactId>
>         <executions>
>           <execution>
>             <id>sign-artifacts</id>
>             <phase>verify</phase>
>             <goals>
>               <goal>sign</goal>
>             </goals>
>           </execution>
>         </executions>
>       </plugin>
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira