- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 14 for hierarchy (0.26 sec)
-
platforms/software/dependency-management/src/test/groovy/org/gradle/api/internal/artifacts/configurations/DefaultConfigurationSpec.groovy
assertBothExistsAndOneIsBeforeOther(hierarchy, middle1, root1); assertBothExistsAndOneIsBeforeOther(hierarchy, middle2, root2); } private static void assertBothExistsAndOneIsBeforeOther(Set<Configuration> hierarchy, Configuration beforeConf, Configuration afterConf) { assert hierarchy.contains(beforeConf) assert hierarchy.contains(afterConf)
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Thu May 23 17:30:13 UTC 2024 - 64.8K bytes - Viewed (0) -
subprojects/core-api/src/main/java/org/gradle/api/Project.java
* #getRepositories()} method to manage the repositories.</p> * * <h3>Multi-project Builds</h3> * * <p>Projects are arranged into a hierarchy of projects. A project has a name, and a fully qualified path which * uniquely identifies it in the hierarchy.</p> * * <h3>Plugins</h3> * * <p> * Plugins can be used to modularise and reuse project configuration.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Thu May 30 04:56:22 UTC 2024 - 74.3K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/releases/upgrading/upgrading_version_8.adoc
* **Roles**: Configuration roles should be set upon creation and not changed afterward. * **Hierarchy**: Configuration hierarchy (`extendsFrom`) should be set upon creation. Mutating the hierarchy prior to resolution is highly discouraged, but is permitted within a `withDependencies` hook.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Fri Jun 07 17:01:07 UTC 2024 - 90.7K bytes - Viewed (0) -
platforms/software/dependency-management/src/main/java/org/gradle/api/internal/artifacts/configurations/DefaultConfiguration.java
validateMutation(MutationType.HIERARCHY); for (Configuration configuration : extendsFrom) { if (configuration.getHierarchy().contains(this)) { throw new InvalidUserDataException(String.format( "Cyclic extendsFrom from %s and %s is not allowed. See existing hierarchy: %s", this, configuration, configuration.getHierarchy()));
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Thu May 23 17:36:01 UTC 2024 - 85.4K bytes - Viewed (0) -
platforms/core-runtime/base-services/src/main/java/org/gradle/internal/service/DefaultServiceRegistry.java
* * <p>Service registries are arranged in a hierarchy. If a service of a given type cannot be located, the registry uses its parent registry, if any, to locate the service.</p> *
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Wed May 29 06:47:40 UTC 2024 - 53.3K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/releases/upgrading/upgrading_version_7.adoc
In order to handle conflicts between nested included build names better, Gradle now uses the directory hierarchy of included builds to assign the build path. If you are running tasks from the command line in nested included builds, then you may need to adjust your invocation. For example, if you have the following hierarchy: ==== [.multi-language-sample] ===== [source,kotlin] ---- . ├── settings.gradle.kts
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Mon Apr 01 15:00:23 UTC 2024 - 87.7K bytes - Viewed (0) -
src/main/java/jcifs/smb/SmbFile.java
Registered: Wed Jun 12 15:45:55 UTC 2024 - Last Modified: Thu May 23 01:50:13 UTC 2024 - 82.3K bytes - Viewed (1) -
src/runtime/malloc.go
// mcentral: collects all spans of a given size class. // mcache: a per-P cache of mspans with free space. // mstats: allocation statistics. // // Allocating a small object proceeds up a hierarchy of caches: // // 1. Round the size up to one of the small size classes // and look in the corresponding mspan in this P's mcache. // Scan the mspan's free bitmap to find a free slot.
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Wed May 29 17:58:53 UTC 2024 - 59.6K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/authoring-builds/gradle-properties/working_with_files.adoc
In other words, you can use a file tree wherever a file collection is required, but remember that a file collection is a flat list/set of files, while a file tree is a file and directory hierarchy. To convert a file tree to a flat collection, use the link:{javadocPath}/org/gradle/api/file/FileTree.html#getFiles--[FileTree.getFiles()] property.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Wed Apr 24 04:19:09 UTC 2024 - 70.5K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/css/javadoc.css
color:var(--block-text-color); } .deprecated-label, .description-from-type-label, .implementation-label, .member-name-link, .module-label-in-package, .module-label-in-type, .package-label-in-type, .package-hierarchy-label, .type-name-label, .type-name-link, .search-tag-link, .preview-label { font-weight:bold; } .deprecation-comment, .help-footnote, .preview-comment { font-style:italic; } .deprecation-block {
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Tue Apr 09 14:25:49 UTC 2024 - 50.5K bytes - Viewed (0)