2Nov/060
Version Control (CVS, VSS, SubVersion, …)
Why doing "Version Control" ?
a) Traceability:
- Who did when what changes?
b) Parallel development:
- Several developers work on the same file on different versions
- Several versions files merged to become a common successor
c) Reproduction of all delivered versions
Version Control functions and requirements:
Check in / check out
Labeling
Textual Difference
Branching
Merging
Views
Search
Reporting
History
Tools:
SCCS (Source Code Control System)
RCS (Revision Control System)
CVS (Concurrent Versions System)
SubVersion (designate successor of CVS Version Control)
VSS (Microsoft Visual Source Safe)
PVCS (Merant PVCS Version Control)
IBM Rational ClearCase
Integration:
See detailed description of "How to Integrate VSS into Eclipse"
« Version Control VSS – Eclipse Integration (Eclipse VSS Plugin)
Affordable conferencing web: ORACLE Internet Seminars »
You might also like
| Quest TOAD 10. ERROR on startup toad.exe: No argument for format ‘%s’ When trying to start up Quest's TOAD, an ERROR occurs: startup of toad.exe No argument for format '%s' See... | Version Control VSS – Eclipse Integration (Eclipse VSS Plugin) How to integrate Microsoft VSS into Eclipse. First you need a VSS environment: a) Install VSS Client b)... | CAST AppInfo Enlighten Trial Version Several months ago I've downloaded a trial version of CAST AppInfo and CAST Enlighthen. We liked to... | Unfortunately a problem with cast nightly Oracle table synchronization on AWmano.exe SYNC CAST Application Mining Error/Problem: Unfortunately, we had to migrate our Oracle databases for several... |
















