刚才说了一下怎么设置EA,用TortiseSVN和Subversion做version control,现在再来简单说一下为什么这么做.
说明一下,这里只是介绍EA通过subversion做version control,和其他的version control类型例如SCC, CVS, TFS还是有一点不同的.
作为EA来说只需要知道"working copy path"(也叫checkout directory)和subversion的可执行文件的path就行了,有没有TortiseSVN都没有关系.
只是TortiseSVN提供了创建Repository和checkout directory的GUI界面而已,其实这两个功能用subversion的命令行也能完成.
一
般来说是在服务器端有一个Repository,然后在本地机器上创建一个checkout
directory.如果安装了TortiseSVN的话,checkout目录的图标上会有一个绿色的钩(说明这是一个正常的checkout目录,如
果目录有错,会显示一个红色的感叹号).
一旦正常创建了checkout目录,就可以在EA里设置version
control了.在EA里面,根据所选的checkout directory创建一个configuration
ID,再根据这个ID给一个Package设置package control.
搞定!!!
为了保证在EA里面正确使用subversion,系统需要安装Subversion, EA和TortiseSVN(TortoiseSVN 为可选).
建议先用EA 30天的试用版试试,盗版的没用过,不知道会不会有问题.
本人安装的版本:
Subversion 1.4.5 (1.3的试过,也行)
TortoiseSVN 1.2.6
EA 7.1.831 (7.0的就行了)
Version Control Configuration
This topic assumes that you have already installed Subversion (both the server and the client parts), and that you have a local working copy
, derived from a repository sub-tree
, already set up for use with your Enterprise Architect model. If this is not the case, please see the
Set up Subversion
topic.
Once you have set up and
tested the Local Working Copy, you are ready to define a Version
Control configuration for use with the Enterprise Architect model to
place under version control.
To apply version control
to your Enterprise Architect model using the Subversion working copy
that you have set up, follow the steps below:
-
Launch Enterprise Architect and open the model for which this Working Copy was created.
-
Select the
menu option.
-
Click on the
button
, enter a suitable name in the
field, then click on the
radio button.
-
To the right of the
field, click on the
button and select the local folder in which to keep local working
copies of the XML files to be stored in the Version Control repository.
-
In the
Workstation Settings
panel, click on the
button to specify the path for your Subversion client executable.
-
Click on the
button to save the configuration you have defined; the new configuration is added to the
Defined Configurations
list.
Note:
|
A new entry is also created in the Local Paths
list, with the same ID as the new version control configuration. The
entry records the Local Project path, for use in subsequent path substitutions.
|
-
When you have finished defining your version control configurations, click on the
button.
Additional Information on the dialog fields:
|
|
This model is private
|
Specify
whether all users connect to a single shared copy of the model (such as
a DBMS) or each user connects to their own private copy of the model.
When unselected (for shared models), the option disables the
File History - Retrieve
functionality when the selected package is checked out by another user.
This prevents modifications that might have been made by the other user
from being discarded through importing a prior revision from version
control.
|
Save nested version controlled packages to stubs only
|
Set nested version controlled packages to stubs or fully expanded trees. Defaults to selected.
For a full explanation of this option, see the
Using Nested Version Control Packages
topic.
|
Unique ID
|
Specify
a configuration name that readily distinguish this configuration from
other configurations. The Unique ID displays as a selection in the list
of Version Control configurations a package can connect to. In addition
you can select a previous version control configuration from this
drop-down menu, providing the configuration is not in the current model.
|
Working Copy path
|
Specify
the folder where the XML files representing the packages are stored.
This folder should already exist before it is specified here.
Every PC using
Subversion version control should have its own Subversion working copy
folder in which to store working copies of the XMI package files; this
should not be a shared network folder. Particularly bear this in mind
if you are creating a .EAP file that is to be shared (for example, a
SQL database).
|
Subversion Exe Path
|
Specify the full path name of the Subversion client executable file.
|
Note:
|
Sparx
Systems strongly urge you not to manipulate version controlled package
files outside of Enterprise Architect. It is possible to leave the
package files in a state that Enterprise Architect cannot recognize.
|
分享到:
相关推荐
SVN版本控制原理SVN版本控制原SVN版本控制SVN版本控制原理原理理SVN版本控制原理
版本控制(Revision control)是一种软体工程技巧,籍以在开发的过程中, 确保由不同人所编辑的同一档案都得到更新。 版本控制透过文档控制(documentation control)记录程序各个模组的改 动,并为每次改动编上序号。...
最新SVN版本控制
SVN版本控制 SVN版本控制 SVN版本控制 SVN版本控制 SVN版本控制
EA中SVN进行版本控制设置步骤,可参考
svn版本控制工具 windows版本 安装版
svn控制版本svn控制版本svn控制版本svn控制版本svn控制版本svn控制版本svn控制版本
自己写的SVN配置(包括SVN服务端)总结,教你怎么安装和配置SVN版本控制、与Apache HTTP Server结合配置、SVN eclipse插件安装配置。讲得很详细(有图解)
svn版本控制指南,svn是当前主流的软件版本控制软件,可以说是cvs的替代品。
本压缩包主要用于清除SVN版本控制,非常好用,直接解压可用,本压缩包主要用于清除SVN版本控制,非常好用,直接解压可用
SVN版本控制工具
SVN是Subversion的简称,是一个开放源代码的版本控制系统,相较于RCS、CVS,它采用了分支管理系统,它的设计目标就是取代CVS。互联网上很多版本控制服务已从CVS迁移到Subversion。说得简单一点SVN就是用于多个人共同...
SVN版本控制系统应用介绍SVN版本控制SVN版本控制系统应用介绍系统应用介绍
Apache Subversion 通常被缩写成 SVN,是一个开放源代码的版本控制系统,Subversion 在 2000 年由 CollabNet Inc 开发,现在发展成为 Apache 软件基金会的一个项目,同样是一个丰富的开发者和用户社区的一部分。...
Eclipse下使用SVN版本控制
SVN版本控制工具入门,介绍, pdf版本。
有svn版本控制的文件,有时候需要修改路径,一层一层的删除文件夹太麻烦,这个小工具,安装之后,右键即可安全删除.svn folder,方便易用。
SVN版本控制工具下载及汉化 带教程