From continuum-users-return-4777-apmail-maven-continuum-users-archive=maven.apache.org@maven.apache.org Wed Sep 26 12:23:42 2007 Return-Path: Delivered-To: apmail-maven-continuum-users-archive@www.apache.org Received: (qmail 44762 invoked from network); 26 Sep 2007 12:23:41 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 26 Sep 2007 12:23:41 -0000 Received: (qmail 61188 invoked by uid 500); 26 Sep 2007 12:23:31 -0000 Delivered-To: apmail-maven-continuum-users-archive@maven.apache.org Received: (qmail 60744 invoked by uid 500); 26 Sep 2007 12:23:30 -0000 Mailing-List: contact continuum-users-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: continuum-users@maven.apache.org Delivered-To: mailing list continuum-users@maven.apache.org Delivered-To: moderator for continuum-users@maven.apache.org Received: (qmail 41536 invoked by uid 99); 26 Sep 2007 12:15:43 -0000 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: domain of dlecan@gmail.com designates 64.233.182.188 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=DNIKwCNfqOPZwdJOwpkkORvQsKuHgmPWfvI3/mCZsIY=; b=D5ndFlwz/dTdHfqHBD6pSzh6Ybs4zxxr+iPAaoxrE2hfF9rr9xz3E9dsYerwTN7Lyy2BXo2AYHPQc4B5MAWt0km4ocbQeYA11o7TAKMDg4EQmbbDOnE0/pQP2Fgyj5qM+nn58nGNmcviKi0j46n/pBUE2eisdcx0pwjEm9LFhpg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=m6aR3JrzsMbzbgkRLIE0tjE7Qs0W83xzqbp0rhWjdKp0RSS6kQxjEMA+NTkqJGx8Ju8WuzHEPGoWyWPoMIaRh30W/IqeicZVfQGU+RidJDRRGfQz99IGdcxhaf0V2EAPsZ28SRYNWz7HyP9lwQXiG4aTFemcEJIeUBQbECxRl8o= Message-ID: Date: Wed, 26 Sep 2007 14:15:21 +0200 From: "Damien Lecan" Sender: dlecan@gmail.com To: continuum-users@maven.apache.org Subject: Re: When builds are done in multi-module projects ? In-Reply-To: <46F8CD17.1010304@venisse.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <46F7A884.4020808@venisse.net> <46F7B479.3020304@venisse.net> <46F7C3B6.301@venisse.net> <46F7C6D3.6030800@venisse.net> <46F8CD17.1010304@venisse.net> X-Google-Sender-Auth: fbd8e7ec0a8f8bdc X-Virus-Checked: Checked by ClamAV on apache.org > You probably have some generated files that aren't in .cvsignore (maybe target) Confirmed : nothing at all [robot@ci 1] cvs status 2>&1 | grep "Status:" | awk '{print $4}' | uniq Up-to-date > If you turn on the log level of org.apache.maven.scm to DEBUG > (maybe org.apache.maven), you'll can see files in logs There is nothing special to see with SCM in DEBUG logs. I have just found this bug : http://jira.codehaus.org/browse/CONTINUUM-1226 I have exactly the same use case, except that continuum builds almost all the time my project, ie even if there is no modification at all. My use case : I have two build definitions in a group: 1. run clean deploy every 4 hours (default) 2. run clean deploy site-deploy every day at 2AM The first one detects real updates from CVS, no problem with it. But the second one sometimes detects unreal modifications. More, I made a test with my build definitions : 1. run clean deploy at 13:00:00 2. run clean deploy site-deploy at 13:15:00 build #1 wrote for each sub-project : ... Merging SCM results The project was not built because no changes were detected in sources since the last build. No changes, not building ... 10 minutes later, no change in CVS, but build #2 wrote : ... Merging SCM results Changes found, building Performing action update-project-from-working-directory Updating project 'My Sub-Project3' from checkout. ... I confirm : nothing was commited between the 2 executions How is this possible ? Something may be wrong when 2 build definitions for the same group are used ? Damien