* limitations under the License.
 */

package org.gradle.api.publish;

import org.gradle.api.Named;

/**
 * A publication is a description of a consumable representation of one or more artifacts, and possibly associated metadata.
 *
 * @since 1.3
 */
public interface Publication extends Named {

    /**

 *         <td>"solaris", "sunos"</td>
 *     </tr>
 * </table>
 */
public interface OperatingSystem extends Named {
    @Input
    @Override
    String getName();

    /**
     * Returns a human-consumable display name for this operating system.
     */
    @Internal
    String getDisplayName();

    /**
     * Is this the current OS?
     */
    @Internal
    boolean isCurrent();

    /**

`assemble` — _lifecycle task_::
Plugins and build authors should attach tasks that produce distributions and other consumable artifacts to this lifecycle task. For example, `jar` produces the consumable artifact for Java libraries. Attach tasks to this lifecycle task using `assemble.dependsOn(__task__)`.

`build` — _lifecycle task_::
_Depends on_: `check`, `assemble`
+

 */
public interface ConfigurationMetadataFactory {

    /**
     * Visit all configurations in this component that can be selected in a dependency graph.
     *
     * <p>This includes all consumable configurations with and without attributes. Configurations visited
     * by this method may not be suitable for selection via attribute matching.</p>
     */

        return convertToId(getDisplayName());
    }

    static String convertToId(String displayName) {
        return displayName.replaceAll("[^a-zA-Z0-9]", "-");
    }

    /**
     * A human consumable display name for this performance test.
     */
    default String getDisplayName() {
        return getExperiment().getDisplayName();
    }

    PerformanceExperiment getExperiment();

    /**

     * a human each child operation of a given operation.
     */
    String getName();

    /**
     * Returns a human consumable display name for the operation. This display name should generally provide enough context
     * to uniquely identify the operation to a human.
     *
     * @return The display name of the operation
     */

        """

        producer.file('build.gradle') << """
            plugins {
                id('java-library')
            }

            configurations {
                consumable("nonLibrary") {
                    attributes {
                        attribute(Category.CATEGORY_ATTRIBUTE, objects.named(Category.class, Category.VERIFICATION))
                    }
                }
            }

====

Capabilities must be attached to _outgoing configurations_, which are <<declaring_dependencies.adoc#sec:resolvable-consumable-configs,consumable configurations>> of a component.

This example shows that we declare two capabilities:

1. `com.acme:my-library:1.0`, which corresponds to the _implicit capability_ of the library

This is where the <<variant_model.adoc#understanding-variant-selection,variant model>> of Gradle comes into play.

In Gradle, _producer variants_ are exposed via <<declaring_dependencies.adoc#sec:resolvable-consumable-configs,consumable configurations>>.

[[sub:strong-encapsulation]]
== Strong encapsulation

In order for a producer to compile a library, it needs all its _implementation dependencies_ on the compile classpath.

        return selectedConfiguration;
    }

    /**
     * Fails the resolution of the project dependency because the selected configuration is not consumable by
     * throwing the appropriate exception.
     *
     * This method is kind of ugly.  If we could get a hold of the ResolutionFailureHandler in this class, we could use the typical