The Winds of Change: Using CVS and Source Code Control
Whoosh! That sounds like the winds of change, or perhaps it is the sound of developers fighting over some code changes. Some of the more popular open-source projects have many developers working on the same sections of code. How do they keep chaos from taking over? There is a very high likelihood that developers will be stepping over each other's code unless there is some system in place to keep track of the changes. All of the open-source communities use some form of source control to manage changes to their files. The configuration management (CM) tools of choice in most open-source projects are CVS and Subversion. These work in similar ways: the programmer checks out copies of source ...
Get Wicked Cool Java now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
