- Sort Score
- Result 10 results
- Languages All
Results 21 - 26 of 26 for variant_model (0.27 sec)
-
platforms/documentation/docs/src/docs/userguide/dep-man/01-core-dependency-management/declaring_dependencies.adoc
2. as a _consumer_, to resolve a set of dependencies to files 3. as a _producer_, to expose artifacts and their dependencies for consumption by other projects (such _consumable_ configurations usually represent the <<variant_model.adoc#understanding-variant-selection,variants>> the producer offers to its consumers) For example, to express that an application `app` _depends on_ library `lib`, _at least_ one configuration is required:
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Thu Dec 07 01:37:51 UTC 2023 - 30.1K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/jvm/java_plugin.adoc
include::sample[dir="snippets/java/apt/groovy", files="build.gradle[tags=annotation-processing]"] ==== == Variant aware selection The whole set of JVM plugins leverage <<variant_model.adoc#understanding-variant-selection,variant aware resolution>> for the dependencies used.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Thu Dec 07 01:37:51 UTC 2023 - 36.1K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/releases/upgrading/upgrading_version_6.adoc
Almost every Gradle project has the _default_ and _archives_ configurations which are added by the _base_ plugin. These configurations are no longer used in modern Gradle builds that use <<variant_model.adoc#understanding-variant-selection,variant aware dependency management>> and the <<publishing_setup.adoc#publishing_components,new publishing plugins>>.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Mon Apr 01 15:00:23 UTC 2024 - 44.8K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/releases/upgrading/upgrading_version_5.adoc
* Variant names must be unique, * Each variant must have at least <<variant_attributes.adoc#variant_attributes,one attribute>>, * Two variants cannot have the <<variant_model.adoc#understanding-variant-selection,exact same attributes and capabilities>>, * If there are dependencies, at least one, across all variants, must carry <<rich_versions.adoc#rich-version-constraints,version information>>.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Thu Feb 22 03:01:48 UTC 2024 - 47.5K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/jvm/java_testing.adoc
==== In this example, we use a convention plugin `myproject.java-conventions` to expose the test results from a project to Gradle's <<variant_model.adoc#understanding-variant-selection,variant aware dependency management engine>>. The plugin declares a consumable `binaryTestResultsElements` configuration that represents the binary test results of the `test` task.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Fri Mar 29 16:24:12 UTC 2024 - 53.1K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/releases/upgrading/upgrading_version_7.adoc
This was <<#unique_attribute_sets,previously deprecated>>. The <<variant_model.adoc#outgoing_variants_report,`outgoingVariants` report>> will warn about this for impacted configurations. ==== Toolchain-based tasks for JVM projects
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Mon Apr 01 15:00:23 UTC 2024 - 87.7K bytes - Viewed (0)