I was looking for some documentation on how to use the tooling in a typical customer environment, where there are multiple developers updating the configuration.
- Do they all have to share the file system where the configuration is stored
- Is there any locking to prevent concurrent changes
If the developers have finished, and we move the sar and aar files towards production. If we find a problem, can we "quick fix" it by importing the files into the "production" tooling, fixing it and exporting it, or do we need to go back to the developers version. The only way I could see of doing it is to use jar to expand the file, edit it manually, and recreate the archive file
regards
Colin
------------------------------
Colin Paice
------------------------------