AccessControl/VersionControl Setup

We recommend to read the relevant section in the Guide for an overview of AnyJs built-in VersionControl/AccessControl system.

It is assumed that all developers operate on the same sources, which can be located somewhere in the LAN.

The version control system distinguishes between two tasks: The "Lock" directory.
This is the directory into which AnyJ puts the filelocks. It should be the same for all developers involved in a project. If a developer opens a file, AnyJ searches this directory for a filelock. If there is a lock, the document will be opened read-only; otherwise AnyJ creates a lock. If a crash happens, this is where locks can be removed (e.g., someone killed the AnyJ task so it wasn't able to remove the locks currently held).

Username
The uername should differ for each machine (e.g., adam@zappa , adam@zero). The developer is identified by this name in the access logs.

Userroot
The userroot is subtracted from every file's path you are about to open. E.g., if you are opening "g:\projects\anyj\source\BlackHole.java" and your userroot is "g:\j11\projects", a lock is created on the file "anyj\source\BlackHole.java".
Another developer, no matter if he uses symbolic links or has just another network drive letter assigned, may access the same file by "z:\mainserver\users\adam\projects\anyj\source\BlackHole.java". This developer should enter "z:\mainserver\users\adam\projects" as a userroot. Thus the access control is able to detect that these files are identical (by removing "g:\j11\projects" from any path of developer A and removing "z:\mainserver\users\adam\projects" from any path of developer B).

The filetypes which are subject to VersionControl can be specified in Global Properties.