- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 56 for produceDirs (0.24 sec)
-
platforms/software/dependency-management/src/integTest/groovy/org/gradle/integtests/resolve/transform/ArtifactTransformInputArtifactIntegrationTest.groovy
createDirs("a", "b", "c") settingsFile << "include 'a', 'b', 'c'" setupBuildWithColorTransform { produceDirs() } buildFile << """ project(':a') { dependencies { implementation project(':b') implementation project(':c')
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Fri Oct 27 19:15:32 UTC 2023 - 51.9K bytes - Viewed (0) -
platforms/software/dependency-management/src/integTest/groovy/org/gradle/integtests/resolve/transform/ArtifactTransformIncrementalIntegrationTest.groovy
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Thu Feb 22 10:57:29 UTC 2024 - 9.5K bytes - Viewed (0) -
platforms/software/dependency-management/src/testFixtures/groovy/org/gradle/integtests/resolve/transform/ArtifactTransformTestFixture.groovy
* ${project.name}FileName - changes the name of the file to write to in the directory * ${project.name}Content - changes the text to write to the output file. */ void produceDirs() { producerTaskClassName = "DirProducer" producerConfig = """
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Fri Oct 20 15:06:39 UTC 2023 - 21.7K bytes - Viewed (0) -
subprojects/core/src/main/java/org/gradle/execution/plan/OrdinalNode.java
* added to the task graph. For example "clean build" on the command line implies that the user wants * to run the clean tasks of each project before the build tasks of each project. Ordinal nodes ensure * this order by tracking the dependencies of destroyers and producers in each group of tasks added to
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Fri Aug 26 20:13:45 UTC 2022 - 2.5K bytes - Viewed (0) -
platforms/core-configuration/model-core/src/main/java/org/gradle/api/internal/provider/MergeProvider.java
@Override public ValueProducer getProducer() { ImmutableList.Builder<ValueProducer> producers = ImmutableList.builderWithExpectedSize(items.size()); for (Provider<R> item : items) { producers.add(Providers.internal(item).getProducer()); } return new MergeValueProducer(producers.build()); } private static class MergeValueProducer implements ValueProducer {
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Fri Dec 15 20:21:34 UTC 2023 - 4.4K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/dep-man/01-core-dependency-management/library_vs_application.adoc
[[sec:understanding-diff-libraries-and-apps]] = Understanding the difference between libraries and applications [[sub:producers-vs-consumers]] == Producers vs consumers A key concept in dependency management with Gradle is the difference between consumers and producers. When you _build_ a library, you are effectively on the _producer_ side: you are producing _artifacts_ which are going to be _consumed_ by someone else, the _consumer_.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Mon Nov 27 17:53:42 UTC 2023 - 5.2K bytes - Viewed (0) -
subprojects/core/src/main/java/org/gradle/execution/plan/MissingTaskDependencyDetector.java
); } } private void collectValidationProblemsForConsumer(LocalTaskNode consumer, TypeValidationContext validationContext, String locationConsumedByThisTask, Collection<Node> producers) { producers.stream() .filter(producerNode -> hasNoSpecifiedOrder(producerNode, consumer)) .filter(MissingTaskDependencyDetector::isEnabled)
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Tue May 28 09:03:53 UTC 2024 - 10.2K bytes - Viewed (0) -
futures/listenablefuture1/src/com/google/common/util/concurrent/ListenableFuture.java
* automate the process, often adding features like monitoring, debugging, and cancellation. * Examples of frameworks include: * * <ul> * <li><a href="https://dagger.dev/producers.html">Dagger Producers</a> * </ul> * * <p>The main purpose of {@link #addListener addListener} is to support this chaining. You will * rarely use it directly, in part because it does not provide direct access to the {@code Future}
Registered: Wed Jun 12 16:38:11 UTC 2024 - Last Modified: Mon Jun 26 21:13:41 UTC 2023 - 8K bytes - Viewed (0) -
guava/src/com/google/common/util/concurrent/ListenableFuture.java
* automate the process, often adding features like monitoring, debugging, and cancellation. * Examples of frameworks include: * * <ul> * <li><a href="https://dagger.dev/producers.html">Dagger Producers</a> * </ul> * * <p>The main purpose of {@link #addListener addListener} is to support this chaining. You will * rarely use it directly, in part because it does not provide direct access to the {@code Future}
Registered: Wed Jun 12 16:38:11 UTC 2024 - Last Modified: Mon Jun 26 21:13:41 UTC 2023 - 8K bytes - Viewed (0) -
platforms/documentation/docs/src/samples/build-organization/cross-project-output-sharing/README.adoc
This publication model is unsafe and can lead to non-reproducible and hard to parallelize builds. By declaring a dependency in this way, the task ordering between consumers and producers is not known to Gradle at the time when it is deciding the order of tasks for a given build. This means that potentially, consumers of the file "someOtherJar" can execute before the producer task that creates the jar!
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Thu Dec 07 01:37:51 UTC 2023 - 2.3K bytes - Viewed (0)