[Anthill] project directory structure question

[Scott W. Ruch]

Upon further consideration, it appears that what
Anthill assumes is that if you check-out a CVS
module named "foo", to your cvs.work.dir, then
there will always be a directory named 
"cvs.work.dir/foo"  Is that a correct assessment?

We are using CVS modules to create virtual projects
which are subsets of the CVS repository - does 
Anthill not support this concept?


> -----Original Message-----
> From: anthill-bounces at lists.urbancode.com 
> [mailto:anthill-bounces at lists.urbancode.com] On Behalf Of 
> Scott W. Ruch
> Sent: Thursday, September 09, 2004 3:03 PM
> To: anthill at lists.urbancode.com
> Subject: [Anthill] project directory structure question
> 
> 
> 
> This appears somewhat convoluted, but bear with
> me.  I'm really not trying to do anything too
> complicated other than organize multiple
> work directories under a common parent directory.
> 
> We have a CVS repository that looks like:
> 
> esm/
>    projectA/
>    projectB/
>    projectC/
>    .
>    .
>    .
>    lib/
> 
> Each projectA,B,C, etc. directory has it's own
> Ant build script and CVS modules are defined as
> such:
> 
> projectA  -a esm/projectA esm/lib
> 
> What I'd like to do is create an Anthill project
> for each module and have Anthill check out each
> module to it's own subdirectory, but I'd like
> them all in one top-level directory under 
> $ANTHILL_HOME, so as to keep things organized.  
> e.g.:
> 
> $ANTHILL_HOME/Inventa/
>                   projectA/
>                   projectB/
> 
> I can't seem to find the correct combination of property
> settings such that Anthill can construct a correct path
> to my version files.  Each module has it's own
> version file under it's main directory, e.g.:
> 
> esm/projectA/projectA.version
> 
> What appears to be the obvious configuration does 
> not work.  If I set:
> 
> repository.cvs.work.dir=Inventa/projectA
> repository.cvs.module=projectA
> 
> Then my module is correctly checked out under
> $ANTHILL_HOME/Inventa/projectA, however, if I
> specify the location of my version.file as:
> 
> version.file=esm/projectA/projectA.version
> 
> which is the path "relative to the project root",
> which I believe to be $ANTHILL_HOME/Inventa/projectA,
> then Anthill fails to find the file because it looks
> in the wrong spot.  Here's the error:
> 
> 14:31:12:105 [Thread - AnthillBuildDaemon] INFO  
> com.urbancode.anthill.adapter.UrbanCodeVersionAdapter  - 
> Incrementing version file:
> /home/build/opt/anthill-1.7.0.162/Inventa/projectA/projectA/es
> m/projectA/projectA.version
> 14:31:12:105 [Thread - AnthillBuildDaemon] ERROR 
> com.urbancode.anthill.BuildManager  - VersionFile parameter 
> must point to a file
> that exists
> java.lang.IllegalArgumentException: VersionFile parameter 
> must point to a file that exists
>         at 
> com.urbancode.anthill.adapter.VersionModifier.<init>(VersionMo
> difier.java:47)
> .
> .
> .
> 
> Note the additional "projectA" in the path that Anthill
> is using to find my version file.  Why is this here?
> 
> Thanks for any insight.
> 
> 
> --
> Scott W. Ruch           ESM Integrator Engineering 
> sruch at inventa.com             Inventa Technologies
> 856.914.5201                http://www.inventa.com 
> 
> _______________________________________________
> Anthill mailing list
> Anthill at lists.urbancode.com
> http://lists.urbancode.com/mailman/listinfo/anthill
>