Return-Path: Delivered-To: apmail-myfaces-dev-archive@www.apache.org Received: (qmail 87761 invoked from network); 27 Jan 2011 08:29:04 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 27 Jan 2011 08:29:04 -0000 Received: (qmail 68706 invoked by uid 500); 27 Jan 2011 08:29:04 -0000 Delivered-To: apmail-myfaces-dev-archive@myfaces.apache.org Received: (qmail 68530 invoked by uid 500); 27 Jan 2011 08:29:02 -0000 Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "MyFaces Development" Delivered-To: mailing list dev@myfaces.apache.org Received: (qmail 68522 invoked by uid 99); 27 Jan 2011 08:29:01 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Jan 2011 08:29:01 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of mwessendorf@gmail.com designates 209.85.215.181 as permitted sender) Received: from [209.85.215.181] (HELO mail-ey0-f181.google.com) (209.85.215.181) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Jan 2011 08:28:53 +0000 Received: by eyh6 with SMTP id 6so938645eyh.12 for ; Thu, 27 Jan 2011 00:28:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=Lz85/04x9zp6SEc8K8cnnx4oCpWXxIM+v0KQXrXgia8=; b=a9fpFRfDKYAJxALEoNxP9vQX3N9YsLibcU094WgiboWlhyFO8HBq4tAOn+cu1G3jik +rueTVgfYFMxZPgHIlAIfcHUF4NHLE2Z84p7LKU7Gec+q3OaFxlidjLq+tsdUFVGWGuB +au+Q5qfQjNGbU6/MDMtZHv7e3S4awj5zOGDs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=haOzFCRft2YvxldwoEDjFSk5ihWdHGfV8D9PXwnPCx8A1ryP6G0zHcAVSn76TemRMl uRhMGEn55MycNAgxeBa31zqZCU/A+wbwwQLzKiu5yDHtBp9Q/xpJj5mA5pRKW/frjcqj eDgZN09ivIj/GcKBmiejlV8RiAPwUAUqfmyik= MIME-Version: 1.0 Received: by 10.213.16.137 with SMTP id o9mr975042eba.31.1296116912594; Thu, 27 Jan 2011 00:28:32 -0800 (PST) Sender: mwessendorf@gmail.com Received: by 10.213.13.18 with HTTP; Thu, 27 Jan 2011 00:28:32 -0800 (PST) In-Reply-To: References: Date: Thu, 27 Jan 2011 09:28:32 +0100 X-Google-Sender-Auth: TTiNHgB3yRWS7aRMbv7--lhYhRg Message-ID: Subject: Re: Maven3 ? From: Matthias Wessendorf To: MyFaces Development Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org Ok, the hosted Maven3.0.2 works fine with the current version of our pom (which now (kinda) requires m3). Most important: the nightly builds works, as they worked before. So, that part would be fixed - for now I am keeping this "improvement", at least temporary. (I will keep 2006 open for a bit, even it looks like we solved it) -M On Thu, Jan 27, 2011 at 9:12 AM, Matthias Wessendorf wrote: > As expected, the build failed locally and on hudson (see > TRINIDAD-2006) due to the site plugin. > > However it is possible to use our Hudson machine with Maven 3.0.2 - > currently I am doing that, > with the patch from TRINIDAD-2006. > > -M > > On Thu, Jan 27, 2011 at 7:16 AM, Matthias Wessendorf wrote: >> Hi, >> >> what are folks thinking about using Maven3. I did some tests for >> Trinidad and Maven 3 yesterday ([1]). >> Things like the regular build and site generation is working fine. I >> am not (yet) 100% how our (Apache) Hudson >> build machine like Maven3 (I used 3.0.2). >> >> However we can simply test that. >> >> I wonder if folks would mind, if the Trinidad build (as a starter...) >> would be "requiring" Maven3.x, in the near future? >> >> Greetings, >> Matthias >> >> [1] https://issues.apache.org/jira/browse/TRINIDAD-2006 >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf