We’re implementing a VCS using Subversion with webMethods. We’re currently running IS 6.5 SP1 on Solaris and Windows boxes. We’ve chosen to go the route of versioning artefacts at the element instead of the package level. The main reason is that we will have some users working directly on our shared developement IS and others working on a local IS. This way we can at least try and detect conflicts that may arrise. (It’s not exactly elegant I know but there’s politics in play).
Anyway I’ve set up scripts that allow us to work this way but I’m having problems activating packages that have been updated and contain .svn folders. On the Windows boxes it works fine - we can update a package out of SVN, the scripts activate the package through some flow service calls and away you go. However when doing the same on the Solaris machines the package activation seems (whilst the admin console reports all is ok) to fail. The strange thing is the IS actually goes and deletes all the flow.xml files from the file system. Weird!
I was just hoping someone might have had some experience with going down this track before. I know it’s possible to change the directory names used by the SVN client (like _svn for a change) but that requires recompiling the client and it would be neater to leave the client unmodified.