Return-Path: Delivered-To: apmail-maven-continuum-dev-archive@www.apache.org Received: (qmail 83089 invoked from network); 29 Aug 2007 09:59:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 29 Aug 2007 09:59:34 -0000 Received: (qmail 25168 invoked by uid 500); 29 Aug 2007 09:59:28 -0000 Delivered-To: apmail-maven-continuum-dev-archive@maven.apache.org Received: (qmail 25143 invoked by uid 500); 29 Aug 2007 09:59:28 -0000 Mailing-List: contact continuum-dev-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: continuum-dev@maven.apache.org Delivered-To: mailing list continuum-dev@maven.apache.org Received: (qmail 25132 invoked by uid 99); 29 Aug 2007 09:59:28 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Aug 2007 02:59:28 -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: local policy) Received: from [62.193.206.9] (HELO webmail9.amenworld.com) (62.193.206.9) by apache.org (qpsmtpd/0.29) with SMTP; Wed, 29 Aug 2007 09:59:23 +0000 Received: (qmail 17984 invoked from network); 29 Aug 2007 09:59:04 -0000 Received: from chb28-2-88-163-39-128.fbx.proxad.net (HELO ?127.0.0.1?) (88.163.39.128) by 0 with SMTP; 29 Aug 2007 09:59:04 -0000 Message-ID: <46D5435F.9020906@venisse.net> Date: Wed, 29 Aug 2007 11:58:55 +0200 From: Emmanuel Venisse User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: continuum-dev@maven.apache.org Subject: Re: error states References: <06289325-D8EE-4B73-B8AB-8485833201AB@apache.org> <46D540D8.50300@venisse.net> <7E4E8CCD-6F72-4A73-AFFC-ED3D13C7ABA6@apache.org> In-Reply-To: <7E4E8CCD-6F72-4A73-AFFC-ED3D13C7ABA6@apache.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org Brett Porter a �crit : > > > On 29/08/2007, at 7:48 PM, Emmanuel Venisse wrote: > >>> 2) rebuild a project that was in error state before. >> >> I think it's the best solution for now and won't be a lot of work. > > agreed... can we sneak this into the 1.1 JIRA? :D sure, I don't think we already have an issue about it (I'll search) so I'll create a new one > >> >>> Only the first would also address the problem of having difficulties >>> diagnosing errors that occur even earlier and don't record a build >>> result at all. It also is a nice separation of >>> configuration/environmental errors vs actual build failures. It helps >>> with the separation of roles when you have a server admin and >>> developers that just commit on the code. >>> However, it's a lot more work, and it might be better to schedule >>> that for the future and fix it via (2) for 1.1. >> >> I'm agree even if I don't know yet how to find the error type. > > Anything that can set an error state on the project needs to be reviewed > to make sure it records a build result if it doesn't already - I've > definitely found some that don't (eg, missing POM parent after scm update) I'll check for the missing POM parent If we have some other case, we'll fix them later. Emmanuel