From dev-return-119586-apmail-commons-dev-archive=commons.apache.org@commons.apache.org Thu Jun 17 14:01:34 2010 Return-Path: Delivered-To: apmail-commons-dev-archive@www.apache.org Received: (qmail 63884 invoked from network); 17 Jun 2010 14:01:33 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 17 Jun 2010 14:01:33 -0000 Received: (qmail 73317 invoked by uid 500); 17 Jun 2010 14:01:32 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 72848 invoked by uid 500); 17 Jun 2010 14:01:30 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 72832 invoked by uid 99); 17 Jun 2010 14:01:29 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Jun 2010 14:01:29 +0000 X-ASF-Spam-Status: No, hits=-0.2 required=10.0 tests=AWL,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of sebbaz@gmail.com designates 72.14.220.158 as permitted sender) Received: from [72.14.220.158] (HELO fg-out-1718.google.com) (72.14.220.158) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Jun 2010 14:01:23 +0000 Received: by fg-out-1718.google.com with SMTP id 22so5114fge.6 for ; Thu, 17 Jun 2010 07:01:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=nt/gNGL8C+87ECVRk+8JAksWLZEHtUUQoJH6mh0TgC4=; b=mm1eKxFDnNPj/L0reGBaAZNnDsz1mSmxaQxyaHZo/mz2DHLZE3J76IuKqkmWZ1WcQ8 h0QtE+XIffBXFCEtOVuZbgXvwc68O7c0Q04rI9jauyxicmv8sJ8aegGob+hbjeJPs7cj N59MhTm3vSVFoN/F+wA/Wni/5SLnbnDwh2NhY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=XL/5oXW0IzERoKizaLRZcyyycUlqHVFrVCMQ7yYV2Nobim7Pk9uAjzH0Xxb1Gwvr1T brdXWfq6GwlPJCQOFXMJI194EyZz/SduHspwO4hInF13+3n79ItEpwI4tIgR04csqWTn 5VOBsDcv7YByDEcNhQbFeGaapJez64qzn6QJ0= MIME-Version: 1.0 Received: by 10.239.188.202 with SMTP id q10mr653652hbh.126.1276783261811; Thu, 17 Jun 2010 07:01:01 -0700 (PDT) Received: by 10.239.187.206 with HTTP; Thu, 17 Jun 2010 07:01:01 -0700 (PDT) In-Reply-To: References: Date: Thu, 17 Jun 2010 15:01:01 +0100 Message-ID: Subject: Re: [ALL] Change deployment override in Commons Parent Pom From: sebb To: Commons Developers List Content-Type: text/plain; charset=ISO-8859-1 On 26/05/2010, sebb wrote: > The Commons parent pom currently overrides the release deployment > descriptor in the Apache parent pom. > > This was done for a very good reason - to prevent accidental > deployments to the live forge. > > However, now that the Apache parent POM uses the Nexus staging > repository for snapshot and release deployments, IMO the Commons > Parent POM actually makes it less safe. > > I think the overrides of the deployment descriptors should be removed > from the Commons Parent pom ASAP - or at least the override should > point to Nexus. > > It would still be possible to use the live forge if really necessary - > by redefining the altDeploymentRepostory property. [Or one could add a > profile to define it]. > > Unfortunately the Commons "release" profile does more than just change > the deployment repository, so one has to use it to create valid > release artifacts. > > Views? > Any objections if I start the process of creating the next version of the parent pom? [i.e. start updating the snapshot pom] --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org For additional commands, e-mail: dev-help@commons.apache.org