I am looking into setting up Version control on Local Service Development. The SAG documentation from Service_Development_Help is a very good starting point, however, there are items that I would like to clarify (this setup is for webMethods 9.7):
Is there a tight dependency between Eclipse plugin version to use and webMethods version? In the document for Polarion plugin is mentioned to use the connector version 3.0.x. The connector version is leading the Plugin version as well, furthermore, also the minimum version of the SVN server.
In other words, I would like to know if it’s advisable to use the latest Polarion plugin + connector and latest support SVN on webMethods 9.7 or this might lead to further issues?
How is the wiring between the assets on the SVN repo and the ones in the local workspace done? Normally, I would see the hidden .svn folders that are used for tracing the differences/status between checkedout assets and the ones on the repository. These files are not present here, but I see that the .project file at the package level (same level with the manifest file) contains:
This could probably be related to keeping the link between the working copy and the SVN, but I am not sure.
Did you face any issues with lock-unlock on server level?
Can you configure at the client level (Designer) automatic update of the working copy after commit/check-out?