Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 37437 invoked from network); 10 Aug 2006 03:22:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 10 Aug 2006 03:22:27 -0000 Received: (qmail 28967 invoked by uid 500); 10 Aug 2006 03:22:26 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 28615 invoked by uid 500); 10 Aug 2006 03:22:24 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 28598 invoked by uid 99); 10 Aug 2006 03:22:24 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Aug 2006 20:22:24 -0700 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of phil.steitz@gmail.com designates 66.249.92.175 as permitted sender) Received: from [66.249.92.175] (HELO ug-out-1314.google.com) (66.249.92.175) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Aug 2006 20:22:24 -0700 Received: by ug-out-1314.google.com with SMTP id m2so411020uge for ; Wed, 09 Aug 2006 20:21:07 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=o4hz/SKjXX4qNYrc0M3M+iTYBlhmXpC2n9ON+YBqF3YMfX8xC0ojR4ePHTRMqlAHOtPt5DRdeVP+SK9K3Yqakxd1JTPtqCo32EaapNrNm4KxcYr7M3qS7A+sybhtZN3Hf+VrqWLssPFqom0EPVDnW84tHMYwaR4UrzuYh80HjL8= Received: by 10.66.221.19 with SMTP id t19mr1970109ugg; Wed, 09 Aug 2006 20:21:07 -0700 (PDT) Received: by 10.66.233.2 with HTTP; Wed, 9 Aug 2006 20:21:07 -0700 (PDT) Message-ID: <8a81b4af0608092021o584f5856mdbd9622cac3ac785@mail.gmail.com> Date: Wed, 9 Aug 2006 20:21:07 -0700 From: "Phil Steitz" To: "Jakarta Commons Developers List" Subject: [nightly build] m2 support - a little help, pls MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N I would like to add m2 support to the nightly build script, but am still an m2 newbie, so could use a little help. I thought that starting with [csv] would be good, since the migration page lists it as "done". I have a couple of questions. 1. It seems to use pom inheritence, which I am sure someone will convince me is a good thing, despite the fact that my first experience with it is a build failure because of it. How do I find and I guess "install" the commons-sandbox-parent? How do we indicate to users that they are going to need to set this up for builds to work? Do we really need this? 2. Properties files seem to be replaced by settings.xml. Is this where we designate repo lists? If so, can someone commit a settings.xml.sample? 3. I assume that the reference to 'minotaur' in the distributionManagement section of the csv pom should be changed to 'people'? Once this is fixed, I assume "deploy" will work correctly using the ssh key that the script is using to connect to people now. 4. The dist plugin seems to be gone and the release plugin looks like it is really just aiming to deploy jars and tag releases. Should I use ant tasks to roll the distros manually or is there some m2 plugin that will do this? Thanks! Phil --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org