See Resolving membership conflicts in a project or project grouping to learn about membership conflicts found in projects or project groupings and how to resolve the conflicts.
ccm conf|conflicts [-r|-recurse] [-v|-verbose][-f|-format format] [-nf|-noformat]
([-ch|-column_header] | [-nch|-nocolumn_header])
[-sep|-separator separator] ([-sby|-sortby sortspec] |
[-ns|-nosort|-no_sort]) [-gby|-groupby groupformat] project_spec
propertyname: Any attribute or built-in keyword for versioned objects.
A specified attribute or built-in keyword value for the versioned object for the conflict. For a task conflict, the attribute is a null value.
propertyname: Any attribute or built-in keyword for projects.
A specified attribute or built-in keyword value of the context project in which the conflict was detected.
The category of the conflict is an abbreviated name that is consistent with the values shown in the GUI. You do not need to specify an object key to use this property name. Use the property name in the format string as %category.
The full description of the type of the conflict is the name that, in prior releases, was shown as the only form of conflict description. You do not need to specify an object key to use this property name. Use the property name in the format string as %description.
ccm conflicts etc-1
Project: etc-1
Objectname Task Conflict Category
abc.java-1:ascii:di#1 di#207 Included by 'use' operation? Extra changes
def.java-1:ascii:di#1 di#207 Included by 'use' operation? Extra changes
etc-1:dir:di#1 di#207 Included by 'use' operation? Extra changes