From dev-return-6900-apmail-continuum-dev-archive=continuum.apache.org@continuum.apache.org Thu Apr 24 03:54:57 2008 Return-Path: Delivered-To: apmail-continuum-dev-archive@www.apache.org Received: (qmail 6940 invoked from network); 24 Apr 2008 03:54:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 24 Apr 2008 03:54:56 -0000 Received: (qmail 71978 invoked by uid 500); 24 Apr 2008 03:54:58 -0000 Delivered-To: apmail-continuum-dev-archive@continuum.apache.org Received: (qmail 71938 invoked by uid 500); 24 Apr 2008 03:54:58 -0000 Mailing-List: contact dev-help@continuum.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@continuum.apache.org Delivered-To: mailing list dev@continuum.apache.org Received: (qmail 71927 invoked by uid 99); 24 Apr 2008 03:54:58 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Apr 2008 20:54:58 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of wsmoak@gmail.com designates 209.85.132.251 as permitted sender) Received: from [209.85.132.251] (HELO an-out-0708.google.com) (209.85.132.251) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Apr 2008 03:54:14 +0000 Received: by an-out-0708.google.com with SMTP id c31so815818ana.30 for ; Wed, 23 Apr 2008 20:54:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=88fgIPKzmibfI1FpSnrK3y7Y+8RKMhJStmY0Soe1Ak8=; b=qaWBzxFj3XC/6LveSJhRbuJ7oSO+39wuOariuH3rY8dWvzgs6/C1h/Bnu8rPITk9p5Y7smoPrWDU+qDj9jzzvJj87/ywTuyHlPJSkEPyLnwFoXz7Cq+F6/bW1P3X1izlBj0BPCNsO0MDVoXvHP47amFYexf3bkdXPQECE2xndhw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=C1Py7csNBrXOp9DSHSeg5cfYgh0vkNvRv5yM5GIh6AYR81lAcnZWoQBhce/h3U9fZi/bzzX1N7LAJ5DsfPSPM3+C198jY1j0iaYBoI7kiIw1kfnNEUQ9uLna1mpyZYqfLmVkHB1CvbP5QaaDemQb1iUicep4nsQvAwNjmOZfqyw= Received: by 10.100.41.9 with SMTP id o9mr4459371ano.42.1209009267185; Wed, 23 Apr 2008 20:54:27 -0700 (PDT) Received: by 10.100.57.14 with HTTP; Wed, 23 Apr 2008 20:54:27 -0700 (PDT) Message-ID: Date: Thu, 24 Apr 2008 11:54:27 +0800 From: "Wendy Smoak" To: dev@continuum.apache.org Subject: Re: Continuum and plain text passwords In-Reply-To: <481001CA.2010509@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <32e018740804232034p33635c83o83cd1e315aa7961b@mail.gmail.com> <481001CA.2010509@gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org On Thu, Apr 24, 2008 at 11:43 AM, Rahul Thakur wrote: > Same thought. > > release.properties is a temporary file used by Maven; if for some reason it > persists, we can choose not to display its contents. Can we apply the filter only to Maven 2 projects? (A shell or ant project might use that filename for something unrelated...) This only solves part of the problem, since if the file exists, anyone with a project developer role could get to it and display it by adding a shell project with a simple script.) What can we do to clean up better after a failed release? (It would be manual, but does the rollback feature even work? IIRC it hung last time I tried it.) -- Wendy