Return-Path: Delivered-To: apmail-shiro-dev-archive@www.apache.org Received: (qmail 97987 invoked from network); 29 Oct 2010 22:59:28 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 29 Oct 2010 22:59:28 -0000 Received: (qmail 97817 invoked by uid 500); 29 Oct 2010 22:59:28 -0000 Delivered-To: apmail-shiro-dev-archive@shiro.apache.org Received: (qmail 97795 invoked by uid 500); 29 Oct 2010 22:59:28 -0000 Mailing-List: contact dev-help@shiro.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@shiro.apache.org Delivered-To: mailing list dev@shiro.apache.org Received: (qmail 97787 invoked by uid 99); 29 Oct 2010 22:59:28 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Oct 2010 22:59:28 +0000 X-ASF-Spam-Status: No, hits=0.7 required=10.0 tests=RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.214.173] (HELO mail-iw0-f173.google.com) (209.85.214.173) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Oct 2010 22:59:22 +0000 Received: by iwn36 with SMTP id 36so4015336iwn.32 for ; Fri, 29 Oct 2010 15:59:00 -0700 (PDT) MIME-Version: 1.0 Received: by 10.42.220.65 with SMTP id hx1mr664129icb.418.1288393140423; Fri, 29 Oct 2010 15:59:00 -0700 (PDT) Sender: les.hazlewood@anjinllc.com Received: by 10.231.168.3 with HTTP; Fri, 29 Oct 2010 15:59:00 -0700 (PDT) In-Reply-To: References: <8B5DC8B3-175A-4B0E-B291-BD2DA464304B@toolazydogs.com> Date: Fri, 29 Oct 2010 15:59:00 -0700 X-Google-Sender-Auth: 08YVVLG4zsqJDbCloc_CmJ4Vm8E Message-ID: Subject: Re: [DISCUSS] 1.1 Release From: Les Hazlewood To: dev@shiro.apache.org Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org It appears I'll have the 2nd-attempt release to vote upon in the next 20 minutes. I had a _hell_ of a time trying to get the gpg signing to work: Even though I set a in my ~/.m2/settings.xml file, the build froze and wouldn't move past the point where it looked up my key. I finally got around the issue by starting the gpg-agent and having to write some bash scripts to start it up based on this: http://www.linuxquestions.org/questions/linux-security-4/gpg-gpg-agent-cant-connect-to-root-gnupg-s-gpg-agent-611843/ Now when I run the build, a screen will prompt me for the gpg password, and I enter it in and it works. Does anyone know why I am prompted for a password even though I have the value set in ~/.m2/settings.xml? Les