Faber Software

This new feature introduces intermediate version control and a ruled access to the project units. This may be useful for both team of developers and single developers who want to track the evolution history of their Faber projects.

Project Version Control

Faber projects may be created or imported under version control by Subversion. A “versioned” Faber project is stored into a central repository, which holds all the intermediate versions. Team developers work on local working copies that refer to the repository.

For example In the picture above two users, Mike and Sally work on the same repository. Two working copies are available and the revision history is the following:

Mike created the project with only two classes and created the repository (revision 1).
Sally checked out her working copy, added a new C module and committed the changes (revision 2), note that the other two classes do not change its revision number.
Mike updated his working copy (retrieving the new C module) then modified the second class; when committed the repository version became 3, but locally the single units have different revision number.

Faber and Subversion

Faber tool integrates both repository communication commands, and project unit statuses in relationship with repository.

Subversion Requirements

Faber tool integrates existent Subversion installations English language version 1.4.5 or more. On Windows systems the Faber installation procedure allows direct installation of Subversion executable and library files needed by Faber.