Mailing-List: contact continuum-users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: continuum-users@maven.apache.org
Received-SPF: pass (athena.apache.org: domain of dantran@gmail.com designates
 209.85.132.246 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=fpLL4a6HwVihfzRLMzsBla651RGMtPKInQNKqsruUAjwyR9miWIvI6cZjBjoJE3lCfVhXE16kxjITCt+uf2CaU3lixQl63SStJbrHncjdWxBQOtUuLdfZQcf8LtFsPCT2w4s1tNnNPKa8ABbS6uBOuFI+4wMrrpT/Fpd+CbBArc=
Message-ID: <c38ad92d0709290745k2862adf6l8835af5f1dae37d@mail.gmail.com>
Date: Sat, 29 Sep 2007 07:45:34 -0700
From: "Dan Tran" <dantran@gmail.com>
To: continuum-users@maven.apache.org
Subject: Re: Get a build when I force but not when I schedule 1.0.3
In-Reply-To: 
 <74C2393513801E43A5A713E6B0BA87AA0193041F@MEMEXCH22V.corp.ds.fedex.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: 
 <74C2393513801E43A5A713E6B0BA87AA0193041F@MEMEXCH22V.corp.ds.fedex.com>

I have seen this behavior on continuum 1.0.3, but have not confirmed
with 1.1 beta.

-D

On 9/28/07, Alex Boyer <alex.boyer@fedex.com> wrote:
> Hi,
>
> When I force a build I get a build in failure for a project, which is
> what I expect.
>
> But if I then allow the default_schedule to start scheduling builds
> every hour I don't get anymore builds. I get this message:
>
> NFO  BuildController                - The project was not built because
> there are no changes.
>
> Well OK. I take it that we don't try a new build even though the
> previous broke since nothing changed.
>
> I deleted a file from the scm repository and waited for the next
> scheduled build.
>
> Same thing. NFO  BuildController                - The project was not
> built because there are no changes.
>
> Even though I can see where the file was deleted because the scm
> changed.
>
> That doesn't make sense.
>
> Folder: BeanService  (working dir: C:\Program Files\Apache Software
> Foundation\continuum-1.0.3\apps\continuum\working-directory\6\src\main\j
> ava\BeanService)
>
> INFO   | jvm 1    | 2007/09/28 16:09:04 | AuthResponse.java: deleted
>
> Then if I force again I see the build error out as expected.
>
> I must be overlooking something.
>
> What makes a build kick off if deleting a file that would break a
> compile doesn't?
>
> Thank you,
>
> Alex Boyer
>
>
>
>