Hi all,
we are planning tp use Subversion for versioning IS Services but are encountering problems having more than one IS connected to the same Repositoriy. Are there any experiences / recommendations connection several IS to the same Subversion repository.
Problems encountered so far:
WmSubversion places a lock on the services checked out but those are not evaluated at checkout time, so several people may work on the same source. When checking in again, all but the first who checked out get an error. As checking in or mering is not possible fpr the later checkouts an error right in the beginnin, when trying to chekcout a locked service would be preferable.
When trying to check in in a service locked by another user the check in fails however the lock in Developer is released. Revert is nout possible and any try to update to the latest version of the reposioty fail with an error “service already checked out”. Cleanup requires action on the server side using svn tools, but server side is usually not accessible for our developers.
.svn directories may cause problems when deploying, especially between Unix and Windows. Deployer does not offer to exclude files from builds. Any ideas there?
Thanks in advance for any inputs on this topic.
Martin
#webMethods#Integration-Server-and-ESB