[Anthill-pro] CVS Module Alias Problems

[Choboter, Kevin]

 Hi Eric,

Thank you for looking into this issue for me. I would like to stay away
from using an ampersand module as it will change the directory structure
of my repository. The subModules would all go into the overall-Module1
directory. This would cause duplication on the build machine as the
subModules are used again in other overallModules.

Sincerely,
Kevin Choboter


-----Original Message-----
From: anthill-pro-bounces at caladin.urbancode.com
[mailto:anthill-pro-bounces at caladin.urbancode.com] On Behalf Of Eric
Minick
Sent: Wednesday, July 05, 2006 12:52 PM
To: anthill-pro at caladin.urbancode.com
Subject: Re: [Anthill-pro] CVS Module Alias Problems

Kevin,

I'll take a look into this. I haven't spent that much time with aliases,
but I know people have used ampersand modules in the past successfully. 
Perhaps that's an easier direction for you.

Anthill doesn't interrogate the alias file to try to unravel the
aliases. My understanding was that the alias names should both retrieve
the files and be useful for revision history, but I'll have to look into
that. I think that if you just had a project with the simple
__submodule1 alias, the directory remapping would work file. My
suspicion is that the combination of aliases plus construction of the
oveall module may be a combination that hasn't been seen before.

I'll see what I can found out on my end, but I would try to configure
the 'overall-module' out of a simple ampersand module.

Regards,
Eric

Choboter, Kevin wrote:

> Hi all,
>
> To clarify a few things in my previous message. The error I get from 
> AHP is "- cvs log: nothing known about* Overall-module1*".
>
> I have tried a few different setups with CVS and Anthill Pro, and none

> of them have worked. In addition to the set-up that I discussed 
> previously, I have attempted to map the CVS sub-modules to checkout to

> a different directory, and then using the CVS working directory script

> to fill in that extra directory. For example, I have the following 
> setup in my CVS modules file:
>
> __subModule1     -d subModule1 repository/subModule1
> __subModule2     -d subModule2 repository/subModule2
> __subModule3     -d subModule3 repository/subModule3
> Overall-Module1     -a __subModule1 / __subModule2 / __subModule3
>
> And then I added /repository to the CVS working directory. Everything 
> does checkout to the correct directories
> (C:\BUILD.work\repository\subModule1 , etc..) but when the IS Build 
> Required Step is run I get the following error message:
>
> ERROR - cvs log: in directory .:
> ERROR - cvs [log aborted]: there is no version here; do 'cvs checkout'

> first.
>
> I have also attempted to use the "CVS Module Directory Remapping" 
> setting in the CVS Driver for the project, by assigning this setting 
> to /repository, leaving the CVS working directory as my base directory

> and having the modules file checkout to repository/sub-Module1, etc..
> However, this configuration seems to ignore my CVS module alias and 
> checkouts everything in CVSROOT/repository.
>
> Is this a known issue in AHP, that the "Is Build Required Step" does 
> not check the CVSROOT modules file and translate aliases to module 
> names or am I doing something incorrect?
>
> Thanks,
>
> */Kevin Choboter/*
> /NCR Waterloo/
> /kc185023 at ncr.com/
>
>
>
>
>
>
>-----------------------------------------------------------------------
>->
>_______________________________________________
>Anthill-pro mailing list
>Anthill-pro at lists.urbancode.com
>http://lists.urbancode.com/mailman/listinfo/anthill-pro
>  
>

_______________________________________________
Anthill-pro mailing list
Anthill-pro at lists.urbancode.com
http://lists.urbancode.com/mailman/listinfo/anthill-pro