何时在RTC源代码管理中使用流中的多个组件 [英] When to use multiple components within a stream in RTC source control
问题描述
我所看到的RTC源控制组件是文件和文件的逻辑分组；文件夹.
何时应在RTC源代码管理中的流中使用多个组件?
方法1:
我有多个java(Eclipse)项目，但我将这些项目添加到单个流中的一个组件中.这些项目被打包到一个部署文件中.
方法2:
每个Java项目都将添加到流中自己的组件中，因此该流将包含多个组件-每个Java项目一个组件.
使用一种方法相对于另一种方法是否有优点/缺点?
RTC组件与 解决方案
An RTC component has really the same meaning than an ClearCase UCM component.
The goal, when using multiple component, is to divide your huge set of files into coherent and logical subsets, more identifiable and manageable.
Example of components:
- an application (or a autonomous part of an application)
- a technical library
- a packaged set of file (for release)
Note: in RTC, you can reuse a component (defined in one project area) in another project area (provided both PA are on the same Jazz server).
A Java project can be represented as one component, but certain Java project could be seen as several components (one for the business logic, one for database logic, and so on)
The main criteria when you define a component is:
Will it evolve at its own pace? Can you modify it without having to modify another component?
(If not, that might mean the two set of files are tightly linked, and might be considered as one component).
From there, you must decide if you want to see all components on one Stream (system approach, with every component writable), or just one or two components per stream (depending on the deliveries - dll, jar, ... - produced by the other components): component approach.
For starter, stick with the system approach, simpler at first.
这篇关于何时在RTC源代码管理中使用流中的多个组件的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
