outputContains "Listed [3, 2, 1] for org:testA"
        outputContains "Supplying metadata for module org:testA:3"
        outputContains "Supplying metadata for module org:testA:2"
        outputContains "Supplying metadata for module org:testA:1"
        outputContains "Listing versions for module testB"
        outputContains "Listed [2, 1] for org:testB"

                expectResolve()
            }
        }

        then:
        succeeds 'checkDeps'
    }

    void "caches version listing using #lister lister"() {
        ListerInteractions listerInteractions
        switch (lister) {
            case 'simple':
                listerInteractions = withLister(modules, true)
                break;
            default:

		be those functions exported using a cgo //export comment.
		Requires exactly one main package to be listed.

	-buildmode=default
		Listed main packages are built into executables and listed
		non-main packages are built into .a files (the default
		behavior).

	-buildmode=shared
		Combine all the listed non-main packages into a single shared
		library that will be used when building with the -linkshared

            throw ResourceExceptions.failure(versionListPattern.getUri(), String.format("Could not list versions using %s.", pattern), e);
        }
    }

    // lists all the values a revision token listed by a given url lister
    private List<String> listRevisionToken(ExternalResourceName versionListPattern, BuildableModuleVersionListingResolveResult result, Map<ResourcePattern, ExternalResourceName> versionListPatterns) {

}

// CheckDir reports whether the files in dir satisfy the name and size
// constraints listed in the package documentation. The returned [CheckedFiles]
// record contains lists of valid, invalid, and omitted files. If a directory is
// omitted (for example, a nested module or vendor directory), it will appear in
// the omitted list, but its files won't be listed.
//
// CheckDir returns an error if it encounters an I/O error or if the returned

      - There are 2 ways to include a new types to this guide:
      -     * Types referenced by a property are automatically included, if there is a corresponding ${typename}.xml in the DSL source directory.
      -     * Types listed in one of the following tables are included. There must be a corresponding ${typename}.xml in the DSL source directory.
      -
      - 2. Adding new sections:

            Circular dependency between the following binaries:
            lib:sharedLibrary
            \\--- util:sharedLibrary
                 \\--- lib:sharedLibrary (*)

            (*) - details omitted (listed previously)
            '''.stripIndent().trim()
    }

    def "indirect circular dependencies are handled gracefully"() {
        buildScript simpleCppBuild()
        buildFile << '''
            model {

                |:a
                |\\--- :b
                |     \\--- :a (*)
                |
                |(*) - details omitted (listed previously)""".stripMargin()
        }
    }

    def "honours mustRunAfter task ordering"() {
        buildFile << """
            task a {
                mustRunAfter 'b'
            }

When a user runs `./gradlew build` in the command line, Gradle will execute the `build` task along with any other tasks it depends on.

== List available tasks

Gradle provides several default tasks for a project, which are listed by running `./gradlew tasks`:

[source,text]
----
> Task :tasks

------------------------------------------------------------
Tasks runnable from root project 'myTutorial'

}

println "My property value: ${project.ext.myProperty}"
----

=== Setting a project properties

You have three options to add project properties, listed in order of priority:

1. *Command Line:* You can add project properties directly to your link:{groovyDslPath}/org.gradle.api.Project.html[Project] object via the `-P` command line option.
+
[source,text]
----