Composer provides limited support for 2 code management (CM) systems:
Before Composer can be to make changes to a local copy of the Method Library, the source files that make up that library must be writable. CM systems usually maintain local files with read-only access unless they have been explicitly marked for editing through the process of checking-out individual files. Source files in the Method Library must be checked-out before they can be edited.
Note: Users in CM-integrated environments should be aware that relatively simple changes to method library elements may affect more than one source file. This implies that multiple files may have to be checked-out before individual method elements can be modified.
Information from the method library is cached in memory when a new library is opened. If library source files are updated outside of Composer the version cached in memory will not be refreshed. In that situation you should reload the entire method library. Alternately the library files can be updated from within the Resource perspective.
As soon as the method library is opened Composer will create two files
named .lock and .project
at the same level as library.xmi.
These two files should NOT be placed under version control.