[Anthill] Re: Anthill Digest, Vol 2, Issue 17

[Chad Woolley]

Randy Bielby wrote:
> Maciej,
>  
> Thanks for your response.  I see your point regarding the idea behind a
> controlled build process.  But, I am trying to migrate an existing build
> process into Anthill.  And, due to corporate culture, team dynamics and size
> of our project,  we pretty much have to have multiple CVS modules.  I am in
> the process of trying to see how dependency groups could work, but that may
> involve changing the way the current build works.  In addition to our build
> philosophy here.  Does anyone know if possibly CruiseControl or Maven may be
> a better fit for us?
>  
> thanks
>  
> --randy

Randy,

I think your problem is that you are trying to have your ant script do the 
checkouts, instead of letting anthill do it.

I have a setup that sounds identical to yours.  However, I manage the multiple 
project via a CVS module that references all the projects.  The anthill project 
then checks this module out (which gets ALL the source), and then there is a 
"masterbuild" script that ties all the other build scripts together.

The one catch is to make sure the CVS module uses the "ampersand" form of reference.

You should be able to use an approach like this, and I think I've described it 
in more detail.  Search the archives (maybe for 'ampersand') and let me know if 
you can't figure it out.

Good Luck,
Chad