Managing work products and generated files

Taking into account modifications in generated files

The Objecteering Multi-user, Objecteering ClearCase, Objecteering SCC, Objecteering CM Synergy and Objecteering Dimensions MDACs do not manage generated files and consider these to be independent files.

In Objecteering, there are three ways of modifying the code of a generated file:

· Modification of notes (C++, Java, etc.)

· Use of the MDAC external edition command

· Modification of generated files outside Objecteering

As regards this third manner of modifying generated file code, a command available for each code generation MDAC must be run, allowing all modifications carried out directly in generated files to be reported to Objecteering.

This command can only be carried out if the modified elements have been checked-out. If a check-in is run on elements without having run this command, all modifications carried out in generated files will be lost.

The Objecteering Multi-user, Objecteering ClearCase, Objecteering SCC; Objecteering CM Synergy and Objecteering Dimensions MDACs all provide the "Update generation work products before check-in" MDAC parameter, used to automatically carry out this code retrieval before running a check-in.

Generating C++ or Java sources in personal environments

In a project managed in multi-user mode, work products are common to all users, and sources are generated in the same directory which is common to all users. In a Windows environment, it is possible to define an identical path for all users, but which is specific to each individual user (for example, "C:\Project\sources"). In this way, even though you have an identical path to all users, each user generates in his own environment.

To solve this problem in Unix, and to define a different generation path for each user (even in Windows), the "Update generation work products after import" MDAC parameter is used to modify each work product after the "Import from repository" command or after a check-out, so that the parameterization of this product be proper to the user.

By activating this parameter, generation paths defined for each work product are updated with the default value (that defined by the parameterization of the C++ or Java MDACs).

Note: This update only concerns C++ and Java work products, for MDACs delivered as standard and for user MDACs inheriting from these two MDACs.