[Anthill] Build for multiple interdependant CVS modules cannot be configured through default gui

[Greg Roll]

Thanks Eric, that was exactly what I was looking for.  I tried it on my 
home machine and found that it works great.   FYI, I found another 
reference that was a little more detailed here: 
http://www.thathost.com/wincvs-howto/cvsdoc/cvs_18.html

Cheers!


Eric Minick wrote:

> Hey Greg,
>
> I think a cvs ampersand  module could get you around the difficulty of 
> having to reorganize the cvs repository. Take a look at this: 
> http://durak.org/cvswebsites/doc/cvs_158.php .
>
> Cheers,
>
> Eric
>
> Greg Roll wrote:
>
>> Yes, thats the obvious solution, but that requires re-organizing the 
>> entire cvs repository, and the loss of all the history.  Althought 
>> that would be the preferred approach, we cannot afford to loose 
>> history.  And to my knowledge, cvs does not let you checkout sub 
>> modules (eg.   projecta/src) which is what we would desire then so 
>> that developers do not need to waste time checking out things they 
>> are not working on.
>>
>> Robert E Dobbins wrote:
>>
>>> You could always define a module that comprises all of your other 
>>> modules!
>>>
>>> Thanks,
>>>
>>> Robert E. Dobbins
>>> IBM Global Services
>>> Systems Management Integration Professional
>>> Web Hosting
>>> redobbin at us.ibm.com
>>>
>>>
>>>
>>> Inactive hide details for Greg Roll 
>>> <groll at chartwelltechnology.com>Greg Roll 
>>> <groll at chartwelltechnology.com>
>>>
>>>
>>>                         *Greg Roll <groll at chartwelltechnology.com>*
>>>                         Sent by: anthill-bounces at lists.urbancode.com
>>>
>>>                         01/31/2005 06:29 PM
>>>                         Please respond to
>>>                         Anthill user list
>>>
>>>     
>>>
>>> To
>>>     
>>> anthill at lists.urbancode.com
>>>
>>> cc
>>>     
>>>
>>> Subject
>>>     
>>> [Anthill] Build for multiple interdependant CVS modules cannot be 
>>> configured through default gui
>>>
>>>     
>>>
>>>
>>> Is there anyway to setup anthill pro to work with multiple cvs 
>>> module base
>>>
>>> modules?.  Our project is very large so the cvs repository is 
>>> structured
>>> with items in different modules.. IE: (bin, src, test, web, app, 
>>> mobile,
>>> docs .. etc)... Unfortunately it seems as though Anthill Pro can 
>>> only be
>>> configured to checkout one module and then fire off the build.
>>>
>>> As a workaround I have it checking out the module with the master
>>> build.xml file (bin) and have my own sub targets to do cvs checkout and
>>> updates on the other required modules before launching the build.
>>>
>>> This works fine, but the downside being Anthill Pro is then unaware of
>>> src changes in the other modules and only fires builds when 
>>> something in
>>> 'bin' changes.  Any alternatives to get this working?.. is this maybe a
>>> feature request that could be included in a future release?
>>>
>>> Thanks,
>>> Greg R.
>>>
>>>
>>> [attachment "groll.vcf" deleted by Robert E Dobbins/Alpharetta/IBM] 
>>> _______________________________________________
>>> Anthill mailing list
>>> Anthill at lists.urbancode.com
>>> http://lists.urbancode.com/mailman/listinfo/anthill
>>>
>>> ------------------------------------------------------------------------ 
>>>
>>>
>>> _______________________________________________
>>> Anthill mailing list
>>> Anthill at lists.urbancode.com
>>> http://lists.urbancode.com/mailman/listinfo/anthill
>>>  
>>>
>> _______________________________________________
>> Anthill mailing list
>> Anthill at lists.urbancode.com
>> http://lists.urbancode.com/mailman/listinfo/anthill
>>  
>>
>
> _______________________________________________
> Anthill mailing list
> Anthill at lists.urbancode.com
> http://lists.urbancode.com/mailman/listinfo/anthill