Fix issue 2451 part #1: https://opends.dev.java.net/issues/show_bug.cgi?id=2451 It is now possible to override the default naming argument for dsconfig sub-commands using the CLI profile in the XML definitions. To do this add the "naming-argument-override" attribute to a relation's CLI profile relation element. For example: <adm:relation name="virtual-attribute"> <adm:one-to-many /> <adm:profile name="ldap"> <ldap:rdn-sequence> cn=Virtual Attributes,cn=config </ldap:rdn-sequence> </adm:profile> <adm:profile name="cli"> <cli:relation naming-argument-override="name"> <cli:default-property name="enabled" /> <cli:default-property name="attribute-type" /> </cli:relation> </adm:profile> </adm:relation>

Update admin framework and dsconfig to support tagging of component definitions as advanced and customizable: * advanced components: these will not be displayed by default in dsconfig. Examples include the various system backends * customizable components: these components are tagged as intended for customization using the CLI XML profile. Customizable components are usually the top level components previously referred to as "generic" by dsconfig. This term confused users who would, for example, mistake a "generic" backend for a JE backend. This change is part of issue 1829.

Fix issue 1884: remove support for operand names in CLI profile.

Add a CLI profile for defining CLI related annotations to managed object and property definitions. The CLI profile defines two annotations at the moment: * the operand name which should be used in sub-command usage help to identify the names of managed objects being added, removed, modified, etc * the list of properties which should be displayed by default in list-xxx sub-commands. For example, when listing connection handlers we can display a summary table that lists the "enabled", "listen-port", and "use-ssl" properties by default Both of these annotations apply only to relation definitions. Existing relations have been updated to include these CLI annotations, although their content is subject to change if we decide that better operand names/default properties exist. These annotations will be used in the forthcoming dsconfig CLI.