include::resolution_rules.adoc[leveloffset=+1]

= Producing and Consuming Variants of Libraries
include::component_capabilities.adoc[leveloffset=+1]
include::feature_variants.adoc[leveloffset=+1]
include::variant_model.adoc[leveloffset=+1]
include::variant_attributes.adoc[leveloffset=+1]
include::cross_project_publications.adoc[leveloffset=+1]
include::artifact_transforms.adoc[leveloffset=+1]

= Working in a Multi-repo Environment

    }

    protected String suggestSpecificDocumentation(String prefix, String section) {
        return prefix + getDocumentationRegistry().getDocumentationFor("variant_model", section) + ".";
    }

    protected void formatAttributeSection(TreeFormatter formatter, String section, List<String> values) {
        if (!values.isEmpty()) {
            if (values.size() > 1) {

- <<dependency_constraints.adoc#sec:adding-constraints-transitive-deps,dependency constraints>>
- <<component_capabilities.adoc#declaring-component-capabilities,component capabilities>>
- <<variant_model.adoc#understanding-variant-selection,variant-aware resolution>>

Publication of Gradle Module Metadata will enable better dependency management for your consumers:

| The configuration used to declare all project dependencies having code coverage data to be aggregated.
| `aggregateCodeCoverageReportResults`
| Consumes the project dependencies from the `jacocoAggregation` configuration using <<variant_model#sec:variant-aware-matching,variant-aware matching>> to find the appropriate test suite type.
|===

| The configuration used to declare all project dependencies having test result data to be aggregated.
| `aggregateTestReportResults`
| Consumes the project dependencies from the `testReportAggregation` configuration using <<variant_model#sec:variant-aware-matching,variant-aware matching>> to find the appropriate test suite type.
|===

include::resolution_strategy_tuning.adoc[leveloffset=+2]

== PRODUCING AND CONSUMING VARIANTS OF LIBRARIES

include::component_capabilities.adoc[leveloffset=+2]
include::feature_variants.adoc[leveloffset=+2]
include::variant_model.adoc[leveloffset=+2]
include::variant_attributes.adoc[leveloffset=+2]
include::cross_project_publications.adoc[leveloffset=+2]
include::artifact_transforms.adoc[leveloffset=+2]

== PUBLISHING LIBRARIES

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>>.