[Anthill] version file - problems when sharing between 2 projects

[Eric Minick]

Michael,

I've recorded this as a bug. The PVCS adapter should be catching this 
and not counting it as a revision. A possible work around is to not use 
the revision file at all and use a property instead. You would use the 
ProjectPropertiesVersionAdapter instead of the standard one. That might  
be problematic if you do builds outside of Anthill and need the version 
there though.

Regards,

Eric

Michael Dunbar wrote:

>I have 2 anthill OS projects corresponding to my 1 "actual" project - one which runs unit tests and one which runs functional tests - because I want to run them on different schedules. I set it up for them to share the same version file (in PVCS), but I noticed that they were running even when no changes were made to the codebase - they were picking up changes to the version file, and building based on that:
>
>09/15/2004 09:46:36	pottery     lines deleted/added/moved: 0/0/0
>	.version: Committed_by Anthill
>
>09/15/2004 10:01:52	pottery     lines deleted/added/moved: 0/0/0
>	.version: Committed_by_Anthill
> 
>
>Since I don't see this problem when only one project is active, I assume each project is building based on changes the other made to the version file.
>
>Has anyone seen this, and can you propose a work around? I thought of either taking the version file out of PVCS (not recommended) or using separate version files (how to keep them in synch?), but am wondering is there is a better way. Any way to tell Anthill to not include the version file when checking revisions?
>
>Thanks,
>Mike
>_______________________________________________
>Anthill mailing list
>Anthill at lists.urbancode.com
>http://lists.urbancode.com/mailman/listinfo/anthill
>
>
>  
>