Visual Paradigm‘s Teamwork Server is designed specifically for perform team collaboration development with Visual Paradigm modeling client. It capable in doing everything you can do with CVS, Subversion, Perforce and ClearCase, plus some exclusive features like task management, online design sharing and comments sharing. You can migrate your teamwork projects from CVS, Subversion, Perforce and ClearCase into Visual Paradigm’s Teamwork Server, including all the revisions and modification histories, and this article will show you how to do the migration. Read more
|Team collaboration development on CVS, SVN, Perforce and ClearCase had been discontinued starting from Visual Paradigm version 13.0|
Visual Paradigm supports performing team collaboration development over different version servers – the Visual Paradigm Teamwork Server, VPository (Teamwork Server on the cloud), Subversion, CVS, Preforce and ClearCase. Customers can choose their favorite versions of server for their tools lineup.
Knowing the type of version server is useful or sometimes essential*. However, as an end user, you may not know the type of version server you are using, just because someone had setup the environment for you. This article will show you how to find out the type of version server you are using.
|This article is out-dated and the support of Subversion had been discontinued since version 13.0.|
If your team uses Subversion server (SVN) to manage your work, and if your server has to use a proxy server to access the internet, you need to edit your servers configuration file to indicate the proxy to use. This article will show you how.
When Visual Paradigm release a new new version, it comes with many new and enhanced features. In order for a project file created in an old version to work smoothly in new version, it has to undergo a conversion process, which involve the checking and patching of project data. The conversion process is a one-off procedure done when you first open the project in new version. It may take a while to complete. So you can imagine if you are working as a team and your team have many, many projects, conversion can be a fairly daunting task.
For this reason, Visual Paradigm introduced the mass project migration feature. It helps you convert a group of projects from old version to new version at the same time, and eventually have them committed to the server automatically. With this, you can assign one team member to execute the mass project migration. And when the migration is complete, ask the rest of the team re-checkout the projects from server. Since the projects have been converted, team members can directly open the project without having to wait for any project conversion, which saves a great deal of time.
Notice that the technique described in this article applies to any users who use Visual Paradigm’s client products (VP-UML/Agilian/Lorigizn) with any kind of supported concurrent versioning system (VP Server, SVN, CVS, Perforce, ClearCase).
|Team collaboration development on SVN had been discontinued starting from Visual Paradigm version 13.0|
Since the file system of Window 7 and Window 2008 Server has been changed recently, thereby, you may encounter difficulties of committing or updating your project with SVN. What you can resolve the problem directly is to disable indexing. In this page, you can learn how to disable indexing when you fail to commit or update project with SVN on Window 7 and Window 2008 Server.
|Team collaboration development on Subversion had been discontinued starting from Visual Paradigm version 13.0|
This article teaches you how to checkout project from self singed SSL subversion server.