- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 26 for variant_model (0.35 sec)
-
platforms/documentation/docs/src/docs/userguide/dep-man/04-modeling-features/variant_model.adoc
Tom Tresansky <******@****.***> 1712091018 -0400
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Tue Apr 02 20:50:18 UTC 2024 - 34.2K bytes - Viewed (0) -
platforms/software/dependency-management/src/integTest/groovy/org/gradle/integtests/internal/component/ResolutionFailureHandlerIntegrationTest.groovy
assertSuggestsReviewingAlgorithm() assertSuggestsViewingDocs("Ambiguity errors are explained in more detail at https://docs.gradle.org/${GradleVersion.current().version}/userguide/variant_model.html#sub:variant-ambiguity.")
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Tue May 28 15:55:38 UTC 2024 - 45K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/dep-man/dependency_management.adoc
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
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Mon Nov 27 17:53:42 UTC 2023 - 2.4K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/dep-man/01-core-dependency-management/viewing_debugging_dependencies.adoc
[[sec:resolving-variant-aware-errors]] === Variant Selection Errors Sometimes a selection error happens at the <<variant_model.adoc#understanding-variant-selection,variant selection level>>. Have a look at the <<variant_model.adoc#sec:variant-select-errors,dedicated section>> to understand these errors and how to resolve them. [[sub:resolving-unsafe-configuration-resolution-errors]]
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Tue May 28 15:55:38 UTC 2024 - 12K bytes - Viewed (0) -
platforms/software/dependency-management/src/main/java/org/gradle/internal/component/resolution/failure/describer/AbstractResolutionFailureDescriber.java
} 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) {
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Wed Feb 28 13:08:22 UTC 2024 - 6.9K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/dep-man/06-publishing/publishing_gradle_module_metadata.adoc
- <<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:
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Fri Dec 01 18:45:05 UTC 2023 - 9.6K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/dep-man/dependency_management_terminology.adoc
Examples of variants each Java components typically offers are _api_ and _runtime_ variants. Others examples are JDK8 and JDK11 variants. For more information, see the section on <<variant_model.adoc#understanding-variant-selection,variant selection>>. [[sub:terminology_attribute]] == Variant Attribute Attributes are used to identify and select <<#sub:terminology_variant,variants>>.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Fri Dec 01 18:45:05 UTC 2023 - 11.5K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/jvm/jacoco_report_aggregation_plugin.adoc
| 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. |===
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Thu Dec 07 01:37:51 UTC 2023 - 5.8K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/dep-man/03-controlling-transitive-dependencies/component_metadata_rules.adoc
The main difference between writing rules and defining dependencies and artifacts in the build script is that component metadata rules, following the structure of Gradle Module Metadata, operate on <<variant_model.adoc#understanding-variant-selection,variants>> directly.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Tue May 28 15:10:53 UTC 2024 - 33.2K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/jvm/test_report_aggregation_plugin.adoc
| 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. |===
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Thu Dec 07 01:37:51 UTC 2023 - 5.6K bytes - Viewed (0)