Search Results

Search found 8 results on 1 pages for 'pvcs'.

Page 1/1 | 1 

  • Visual Studio 8, PVCS or Rational ClearCase

    - by Stephen Swensen
    We are currently using Visual Studio 8 with Visual Source Safe. Due to customer requirement, we must migrate to either PVCS or Rational ClearCase, Team System is not an option. Please recommend one of these two options, giving pros/cons from experience with each. How well does each integrate with Visual Studio 8?

    Read the article

  • PVCS 6.0 Checkout with Folder Heirarchy

    - by ybelsare
    Hi , We are using PVCS 6.0 in our current project . I want to checkout the complete project along with the folder heirarchy into my working directory . currently if i select the project and do a checkout , it just dumps all the file into my working folder without any heirarchy . Any idea about how to go about this ? ... any help is appreciated

    Read the article

  • Can I migrate from ClearCase to Serena VM?

    - by Rich B
    I have a repository using Rational ClearCase Explorer 2003.06.10+ which I want to migrate into Serena ChangeMan Version Manager 8.1.4.2. Is this possible? The ClearCase repository was not used for all it's functions, just as a place to hold copies of documents, so the only thing I need to keep is the files and their version histories.

    Read the article

  • webui for mercurial (hg)

    - by Extreme
    i'm looking for a good webui tool for mercurial. i've found this link Mercurial with WebUI but what i'm looking for is something that has the ability to do check-in and check-out per file like the PVCS. any suggestions? thanks Edit: Here's the link for PVCS. http://en.wikipedia.org/wiki/PVCS It's been around 4 years since I last used PVCS and a lot has probably changed but here's as far as I remember. It has a web application wherein a developer can check out a single file. If this file is checked-out, it will be locked to this developer and no other developer can check it out. Then can download the source but they won't be able to check it in unless the original developer (that checked-out the file) checks it in.

    Read the article

  • Attach labels to items in TFS from the PowerBuilder IDE?

    - by DaveE
    We do this using the 'Advanced' button on the checkin dialog now (with Merant, nee PVCS) but the 'Advanced' button is disabled when I set TFS as my SCC provider. Is there a switch we can flip on either side to enable this? Or do we need to write some custom extension? Or can I get the TFS changeset number to associate with the change in PB? Or am I coming at doing selective builds entirely the wrong way?

    Read the article

  • Source Control Checkin Comments at Top Of Source Files

    - by James Wiseman
    I've noticed a discrepancy with some source files in our system whereby some contain source-control checkin comments, and some do not. These comments are added automatically to the top of the file when it is checked in: * $Log: //vm1/Projects/Morpheus/Sleep.bdy-arc $ -- -- Rev 1.14 Apr 14 2009 15:32:52 John Smith --Fixed bugs 2292 and 2230. This seems to have been quite prevelant in all the compainies with which I have worked, but I must confess that I struggle to see the point. Generally the comments aren't that good, are ofen left by people who have long since departed, and even when they are of a high standard it is difficult to tie them to physical code changes. It also strikes me, that you are physically changing the file that you are checking in. Now, this may not be such a problem with files that will be compiled, but could be a disaster with others, e.g. JavaScript files. So really, my query is what was the motivation in concept behind providing this functionality in the first instance? Does anyone actually find these comments useful? Also, I would be curious to know if this was feature that is commonly supported within Source Control systems. I am aware of it with PVCS, VSS and Subversion (Subversion Keyword Substitution), however I wonder if it is also available in some of the more popular DVCSs. Your help, as always is much appreciated.

    Read the article

1