This week's book giveaway is in the OCPJP forum. We're giving away four copies of OCA/OCP Java SE 7 Programmer I & II Study Guide and have Kathy Sierra & Bert Bates on-line! See this thread for details.
Working with the Ant PVCS task is more than cumbersome. I think that the Ant's integration with PVCS lacks a lot of useful features. I found only get and getlatest options. Aditionally I have a lot of problems accessing the PVCS repository because of authentication issues. Does Ant Developer's Handbook go deeper into how to use Ant with PVCS?
What other PVCS features are you looking at other than 'get'?? I have been using ant with PVCS for quite a while now.... everything went on pretty smoothly... [ March 11, 2003: Message edited by: boon boh ]
I don't use PVCS any more (I have now moved to another project team who use Continuus, which is worse! ), but I used to face this sort of problem all the time. Ant support for version control seems to be centred on the idea that all files will be created/extracted, edited and checked in to the repository manually, and the only job of Ant is to pull out a complete source tree and build it. While this may be a reasonable choice for some situations, for me its upside down. What I would like is a way to simply edit, refactor, create and delete files in my "work area", then use Ant to build the application and run the unit tests. If/when the unit tests pass, I would like Ant to handle booking in any changes, creating repository entries for any files which are new, deleting entries for any files which have been removed, and tagging the final repository state with some version tag. I really dislike the idea of having files in the repository which haven't been tested, or are incompatible with others. I want freedom to refactor and run my tests before I check files in, and I want ant to take care of the tedious job of making sure the repository matches the code I have just tested. Any suggestions ?
I have been using the pvcs task successfully. I have even modified the pvcs task to use "pcli get" instead of the old "get", for which the support has been removed by our support team. I use PVCS vm version 7.5. Chandrakumar
Is there any way to automatically apply a version label using the ANT pvcs task so that a build number can be automatically assigned to the current version of all files in a project ? I guess it would be relatively easy to extend/create an task to use the PCLI commands but I would rather not reinvent the wheel Thanks
Andy Bowes<br />SCJP, SCWCD<br />I like deadlines, I love the whoosing noise they make as they go flying past - Douglas Adams