[Anthill] Bug in PVCS or Anthill (with the version file)?

[McKerral, Cameron]

Rob (and Eric),

I had a similar problem last week and found the solution to my problem at ...
http://lists.urbancode.com/pipermail/anthill/2003-June/001585.html

Essentially the problem was that the version file was checkout by anthill, then updated/incremented, but for some reason anthill was setting the base project incorrectly (and unnecessarily).  So the solution for me was to go to the <anthill>\conf\profiles\Win32\win_pvcs\postEditPagelet.pgl file and removed the unnecessary "-bp<filepath>" entry.

This definitely sounds similiar to your problem ... and if you look in the tomcat logs you can see the exact command being called ("pcli ...") and see the pvcs error that it is returning.  You can also see the anthill puts on a version description of "Committed_by_Anthill" when it checks it in.

I now have a separate problem which is around PVCS labelling, but haven't had a chance to look into it yet .... I'm fairly new to anthill, but all and all it looks like a very powerful and flexible product.  Great work guys!

Hope this helps.

Regards,
Cam
-----Original Message-----
From: anthill-bounces at lists.urbancode.com
[mailto:anthill-bounces at lists.urbancode.com]On Behalf Of Eric Minick
Sent: Friday, 21 January 2005 2:35 AM
To: Anthill user list
Subject: Re: [Anthill] Bug in PVCS or Anthill (with the version file)?


Hi Rob,

Thanks for the detailed description. I can compare what we do in OS to 
what's done on the Pro side and see if it is just missing a checkin 
comment. Perhaps it used to be optional and is now required.

You can track the version number in a property, insead of a file if 
you'd like. You'd want to replace the UrbanCodeVersioningAdapter with 
com.urbancode.anthill.adapter.ProjectPropertyFileVersionAdapter . In 
that case, your version number is just stored in the property files.

Thanks,

Eric

Rob Stark wrote:

> Hi There,
> I recently installed the latest version of Anthill OS and hooked up my 
> project to use the PVCS version manager repository (on a Windows 2000 
> server).  I followed the instructions and searched the web on the 
> following, and it appears the issue has been talked about once before 
> but no solution was ever mentioned.  I'm hoping maybe someone can 
> point me in the right direction.
>  
> During a build of Anthill (1.8.??), the code is successfully 
> downloaded from the PVCS repository.  Anthill next check's out the 
> version file to read the file and update it.  Anthill next tries to 
> check the file in but fails to do so.  I'm fairly certain that the 
> reason had to do with the fact that PVCS is requiring a description 
> (or a comment) for the change to the file being checked in.
>  
> Is there a way to resolve this descrepency for anthill?  I'm thinking 
> I might need to setup a config file for PVCS to disable this feature 
> or provide some kind of (PVCS default) evironmenn variable on the 
> server, that will either allow me to disable the comment being 
> required or pass in a generic comment.  I don't yet know how to 
> resolve the issue as the command line docuemntation for PVCS seems a 
> little sketchy/criptic.
>  
> Any thoughts or help is greatly appreciated.  The error in the eror 
> log suggests that anthill is unable to unlock the file and when I log 
> into PVCS I see the .version file still locked.  Essentially the 
> Anthill build process is frozen and never recovers.
>  
> Any help/guidance is appreciated.
> Regards,
>  
> ~Rob
>
>------------------------------------------------------------------------
>
>_______________________________________________
>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