Working with Files

Operations in Compatible Work Areas

Using “compatible” work areas you can use different Dimensions clients to perform source control operations, such as file check in and check out. You can also use the other clients to deliver changes and update local work areas.

If you perform source control operations outside eclipse that change the local files and metadata or change the repository, you must refresh the Eclipse display and internal caches to reflect this. Use the Team | Refresh Status menu option at the Eclipse project level to ensure that the status is current.

Serena Dimensions for Eclipse uses project specific upload rules when delivering new files. These rules specify the item type, item format and owning design part for new items. These rules are created whenever an Eclipse project is shared with Dimensions CM. Whenever new files are added within the scope of a shared Eclipse project, the original upload rules for that project will be used, regardless which client performs the action

Serena Dimensions for Eclipse does not consider derived resources as candidates for source control. However, when using other Dimensions clients, these files may be considered as candidates for source control. The default exclusions filter on the Dimensions Synchronize wizard excludes common java derived artifacts such as class, jar and war files from source control. Take care to exclude these files if you have changed the Synchronize wizard filter, or if you are using the command line interface.

NOTE: If you are performing cross-stream merges including deletions and file renames/moves, then this operation and the following delivery back to Dimensions CM must be performed completely in either Eclipse or the other Dimensions client.

NOTE: If you are using Dimensions projects, Serena strongly recommends that you use the Serena Dimensions for Eclipse to perform check-in operations. Serena Dimensions for Eclipse maintains and expects a single line of descent in Dimensions projects and this is not supported in other Dimensions CM clients. If you get branches in the pedigree of an item in a shared Eclipse project, you will need to resolve this to maintain a single tip revision within the Dimensions project.