that switch just kills the processing of modules during the building
of that module, which is fine since the modules exist as other
projects in continuum and get their own build cycle/definition.

are you having a problem or something?

On 1/23/07, AyoContinuum <[EMAIL PROTECTED]> wrote:

would I have to take out the --non-recursive switch in the build goal of the
projects



Jesse McConnell wrote:
>
> thats the default behavior...it monitors for changes on the target
> scm, when it detects changes it rebuilds that module, and any module
> using that module as a dependency (in m2 projects)
>
> jesse
>
> On 1/23/07, AyoContinuum <[EMAIL PROTECTED]> wrote:
>>
>> Does any body have an idea of setting up an auto detect with
>> continuum...goal
>> is for continuum to build projects upon commit of code by developer to
>> CVS.
>>
>> Basically Continuum monitors cvs projects and triggers build upon commit
>> of
>> new code to project.
>>
>> Thanks
>> --
>> View this message in context:
>> http://www.nabble.com/Auto-detect-with-continuum-tf3065343.html#a8525555
>> Sent from the Continuum - Dev mailing list archive at Nabble.com.
>>
>>
>
>
> --
> jesse mcconnell
> [EMAIL PROTECTED]
>
>

--
View this message in context: 
http://www.nabble.com/Auto-detect-with-continuum-tf3065343.html#a8526805
Sent from the Continuum - Dev mailing list archive at Nabble.com.




--
jesse mcconnell
[EMAIL PROTECTED]

Reply via email to