Workarounds: Enterprise Extensions problems in Rational Team Concert 4.0.3
Build basis: Rational Team Concert 4.0.3
The following known problems are related to Enterprise Extensions in the Rational Team Concert 4.0.3 release.
Workarounds
The following problems in this release have workarounds:
- Dependency builds fail because of source code data scanning errors
- Build subset ownership and visibility change without warning
Workaround summary
By default, a dependency build fails if the source code data scanner fails to scan a file.
Authors: Hung Lam, Stephanie Taylor
Last updated: 28 May 2013
Problem
Dependency builds require that the source code data service scans source files before processing the files for the build. When the source code data service fails to scan a file, the dependency build stops and fails.Workaround
There are two ways that you can resolve this problem:- Open the language definition that is associated with the file that was not scanned. On the Source Code Scanners list, remove Default Scanner for System z and replace it by adding Previous Default Scanner for System z (deprecated).
- From the Jazz Team Server administrative console, in theAdvanced Properties section, change the value of the Continue Source Code Data Scanning On Error property to true. (The default value is false.)
Related information
Workaround summary
Author: Stephanie Taylor
Last updated:
Problem
In Rational Team Concert version 4.0.3, the Enterprise Extensions build subsets function is expanded so that you can assign ownership and control the visibility of build subsets. However, if a member of your team uses a previous version of the client and changes a shared build subset, subset ownership automatically changes to that user and visibility automatically changes to scoped (public) without warning. When ownership changes because of the older client, the original build subset owner can no longer modify the subset and the new owner cannot change ownership back to the original owner without first upgrading to a 4.0.3 client.
Workaround
To avoid problems with shared build subsets, all users who access shared build subsets must upgrade to a version 4.0.3 client.
If a member of your team inadvertently changed subset ownership and scope by accessing a subset with an older client, that team member can restore ownership and scope by upgrading to a version 4.0.3 client first and then resetting ownership and visibility.
Copyright © 2013 IBM Corporation