CBE is revision control system with integrated make-like functions written in pure Java. It can be used similar to CVS but offers some new features like renaming files (while still keeping the history) and using a database as backend (optional).
CBE is released under the GNU GPL and the source code is available from the SourceForge project page
Since CBE is written in Java it has to be started by using the shell-script cbe or by using "java cbe.CBE ..." (requires cbe.jar in your CLASSPATH). Here it is assumed that the script is used.
To create a new project you can use the following:
cbe init /repo/myproject
cbe checkout /repo/myproject
cbe add cpp *.cpp
This is similar to CVS, the main difference is the parameter "cpp" after "cbs add" which places the files in a certain configuration (explained below, can be changed at any time)
Somewhat unusual about CBE is the fact that every file is placed in a configuration describing the type of the file. This is used by the make system to determine how to handle a file. If you do not want to use configurations you can place all files in a configuration (e.g. default) and ignore the configuration; it is determined with add (or reconfigure) and only used by make)
Using CBE as a make system
CBE can be used as a make system (even without using it as a revision control system, just add files and do not commit) by using "cbe make
Using CBE with a database backend
CBE can either be used file-based (like CVS) or with a database backend (this can be changed at any time in both ways). CBE requires a ODMG conforming object-database and currently recognizes SOD, just give "sod://..." as repository name to use the database.