1. Version Control CSC 517 John Slankas

2. Version Control Managing files and directories, and the changes made to them over time. - Adapted from “Version Control with Subversion”

3. Why Use it Personally? History Backups Snapshots

4. Why Use it as a Team? Personal benefits Multiple developers Merge changes Who did what?

5. Available Repositories RCS / SCCS CVS Subversion Visual SourceSafe Git Rational ClearCase CA Harvest And many, many more

6. Which One to Use? What capabilities are needed? What is available? What is my budget? What intergrates with my IDE? What comes with my IDE? Do I have to use something?

7. Subversion (SVN) Successor to CVS Well-adopted in the open source community Client-server based NCSU’s CSC Department provides an environment

8. Eclipse Plug-in Installation Two components (for Subversive) –Plug-in –Connector Configure repository Instructions available on course website Subclipse is available as well (http://subclipse.tigris.org)

9. Demo Start VCL Start Eclipse New project, import StringUtil file Configure Subversion Put project under version control Make code change and commit View history and compare versions

10. Branches and Tags Branches: Isolate changes to another development line Tags: Snapshot of the content Image: http://en.wikipedia.org/wiki/Subversion_(software)

11. Exercise 3: jUnit & Version Control Install Subversive plug-in and connectors (Not necessary on the VCL image) Configure Subversive against the CSC Repository URL: https://svn.csc.ncsu.edu:8443/svn/csc-517-untiyidhttps://svn.csc.ncsu.edu:8443/svn/csc-517-untiyid Create a new Java project Import the StringUtil class Create a jUnit test case for StringUtil that tests a “normal” run of the reverse() method. (i.e., reverse(“hello”) returns “elloh” ) Check in the project to SVN Run your test case. Fix code as appropriate. Commit changes. Add another test case for passing null to reverse() Run your test cases. Fix code as appropriate. Commit changes. Compare the two versions of the StringUtil class