Mailing-List: contact users-help@continuum.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@continuum.apache.org
Received-SPF: pass (nike.apache.org: local policy)
From: Christian Edward Gruber <cgruber@israfil.net>
To: users@continuum.apache.org
In-Reply-To: <17206683.post@talk.nabble.com>
Subject: Re: Managing project group default build definition
References: <17206683.post@talk.nabble.com>
Message-Id: <3FC54D26-50A7-43FF-A74E-842D76D65533@israfil.net>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Tue, 13 May 2008 08:39:37 -0400
Cc: continuum-users@maven.apache.org

I tend to make a default build schedule that executes sometime in 2063  
or something and that's the default, then selectively apply other  
schedules to per-project builds if I'm in that situation.  Or I move  
all the pom projects into other groups on Continuum.

Christian.

On 13-May-08, at 07:55 , Arnaud Bailly wrote:

>
> Hello Continuum,
> I have a bunch of projects organized in the usual maven2 hierarchy  
> that I
> build on continuum. I came across the issue
> http://www.nabble.com/multimodule-project---parent-building-because-of-source-changes-in-child-td16592202.html 
> .
>
> To get rid of it without patching continuum, I want to schedule pom  
> projects
> on a daily basis, and other projects on a hourly basis. The problem  
> then is
> how can I override the default build definition for the project  
> group ? I do
> not want to have two builds for leaf projects, one daily and the other
> hourly.
>
> Best regards,
>
> Arnaud Bailly
> -- 
> View this message in context: http://www.nabble.com/Managing-project-group-default-build-definition-tp17206683p17206683.html
> Sent from the Continuum - Users mailing list archive at Nabble.com.
>