Another particularly important configuration element is link:{groovyDslPath}/org.gradle.api.artifacts.ResolutionStrategy.html[resolutionStrategy], which can be accessed from dependency configurations.
This provides many of the features you might get from Ivy's conflict managers and is a powerful way to control transitive dependencies and caching.
+
Some Ivy configuration options have no equivalent in Gradle.

It is required because the settings file defines which projects are taking part in a <<multi_project_builds.adoc#multi_project_builds,multi-project build>>.
Besides defining included projects, you might need it to <<organizing_gradle_projects.adoc#organizing_gradle_projects,add libraries to your build script classpath>>.

The following example shows a standard Gradle project layout:

====
[.multi-language-sample]

            tasks.register<CheckDeps>("checkDeps") {
                files.from(configurations.compileClasspath)
                expected.set(listOf("lib-core-1.0.jar", "lib-ext-1.0.jar"))
            }
            // Might be worth checking constraints too? Not sure if necessary because the Groovy DSL version covers that
            // and the selected versions above would be wrong.
        """

        expect:
        succeeds ':checkDeps'

The same applies to the scenario in which something in the _buildSrc_ directory changes, which invalidates build-script caching.
Builds with slow configuration time might affect the IDE responsiveness, please check out the <<performance.adoc#performance_gradle,documentation on Gradle performance>>.
* You must run Gradle with Java 8 or higher. Java 7 is not supported.

         * On close, we remove our details from info region and release the exclusive lock on the state region.
         * <br><br>
         *
         * Note: In the implementation we use {@link java.nio.channels.FileLock} that is tight to a JVM process, not a thread.
         */
        private LockState lock(LockMode lockMode) throws Throwable {

  // that our format is used.
  //
  // The second argument of DefaultPrintTo() is needed to bypass a bug
  // in Symbian's C++ compiler that prevents it from picking the right
  // overload between:
  //
  //   PrintTo(const T& x, ...);
  //   PrintTo(T* x, ...);
  DefaultPrintTo(IsContainerTest<T>(0), is_pointer<T>(), value, os);
}

Composite (include) builds are great for separating build logic (i.e., convention plugins) or testing systems (i.e., patching a library)

[.text-right]

**Step 3 - Configure your system environment**

To install Gradle, the path to the unpacked files needs to be in your Path.

In **File Explorer** right-click on the `This PC` (or `Computer`) icon, then click `Properties` -> `Advanced System Settings` -> `Environmental Variables`.

Under `System Variables` select `Path`, then click `Edit`.

     * actually uses.
     *
     * Apart from the obvious classes that are directly used by the other set, we also need to keep any classes that might affect any number
     * of classes, like package-info, module-info and inlineable constants.
     */
    public ClassSetAnalysisData reduceToTypesAffecting(ClassSetAnalysisData other, CompilerApiData compilerApiData) {

            return DynamicInvokeResult.notFound();
        }

        @SuppressWarnings("MixedMutabilityReturnType")
        // This might be too invasive to fix properly because it is in the dynamic code.
        public Map<String, ?> getProperties() {
            if (!includeProperties) {
                return Collections.emptyMap();
            }