Showing object conflicts for a project

You can show the object conflicts in a project.

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.

About this task

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
-ch|-column_header
Specifies to use a column header in the output format. The default is -ch|-column_header. See -ch|-column_header for details.
-f|-format format
Specifies the command output format. See -f|-format for details.
The format string specified by the command is processed by a data formatter. If there are multiple kinds of objects to be formatted based on a CLI command, then the format string must specify the properties to be displayed. Use an objectkey keyword with the following form: %[objectkey]propertyname.
The objectkey specifies the part of the object that the named property refers to. The propertyname is an advanced keyword. The following list shows the supported object keys and property names for the conflicts command:
  • objectkey: object

    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.

  • objectkey: project

    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.

  • propertyname: category

    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.

  • propertyname: description

    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.

-gby|-groupby groupformat
Specifies how to group the command output. See -gby|-groupby for details.
-nch|-nocolumn_header
Specifies not to use a column header in the output format. See -nch|-nocolumn_header for details.
-nf|-noformat
Specifies not to use column alignment. See -nf|-noformat for details.
-ns|-no_sort
Specifies not to sort the output. See -ns|-nosort for details.
project_spec
Specifies the project to analyze for membership conflicts. You can set project_spec to one project only. See Project specification for details.
-r|-recurse
Specifies to show membership conflicts in all projects in the hierarchy for the specified top-level project.
-sep|-separator separator
Used only with the -f|-format option. Allows you to specify a different separator character. See -sep|-separator for details.
-sby|-sortby sortspec
Specifies how to sort the command output. See -sby|-sortby for details.
-v|-verbose
Specifies to display detailed messages showing the steps and analysis of the membership conflicts.

Example

Show the conflict detection information for the etc-1 project.

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	

Feedback