example.com/latemigrate/v2 v2.0.1
written by hand

This repository migrated to modules in v2.0.1 after v2.0.0 was already tagged.
All versions require rsc.io/quote so we can test downgrades.

v2.0.1 belongs to example.com/latemigrate/v2.

-- .mod --
module example.com/latemigrate/v2

require rsc.io/quote v1.3.0
-- .info --
{"Version":"v2.0.1"}
-- go.mod --
module example.com/latemigrate/v2

require rsc.io/quote v1.3.0
-- late.go --

# Check that go line in go.work is always >= go line of used modules.

# Using an old Go version, fails during module loading, but we rewrite the error to the
# same one a switching version would use, without the auto-switch.
# This is a misconfigured system that should not arise in practice.
env TESTGO_VERSION=go1.21.1
env TESTGO_VERSION_SWITCH=switch
cp go.work go.work.orig
! go list

    @Suppress("DEPRECATION")
    @Deprecated("Will be removed in Gradle 9.0")
    override fun module(notation: Any): Dependency =
        delegate.module(notation)

    @Suppress("DEPRECATION")
    @Deprecated("Will be removed in Gradle 9.0")
    override fun module(notation: Any, configureClosure: Closure<Any>): Dependency =
        delegate.module(notation, configureClosure)

    override fun project(notation: Map<String, *>): Dependency =

        }

        void addChecksum(HttpModule module, String algo, String type = "jar", String ext = "jar", String origin = null, String reason = null) {
            def checksum = getChecksum(module, algo, type)
            doAddChecksum(module.group, module.module, module.version, type, ext, algo, checksum, origin, reason)
        }

        originalResult.rootIdeaProject.modules.name == ['buildA']

        def moduleA = originalResult.rootIdeaProject.modules[0]
        moduleA.dependencies.each {
            assert it instanceof IdeaModuleDependency
        }
        moduleA.dependencies.targetModuleName == ['buildB-b1', 'buildA-buildC', 'buildD-b1']

        originalResult.getIdeaProject('buildB').modules.name == ['buildB', 'buildB-b1', 'b2']

--
Resolution can only be made in favor of a module _found_ in the graph.

The `select` method only accepts a module found in the _current_ candidates.
If the module you want to select is not part of the conflict, you can abstain from performing a selection, effectively not resolving _this_ conflict.
It might be that another conflict exists in the graph for the same capability and will have the module you want to select.

// ConvertXlaCallModuleOpToBfloat16Pass works on XlaCallModuleOps with
// serialized modules. Which makes verification difficult. Therefore we add
// (de)serialization passes so that the input and output are deserializated
// StableHLO functions.

// CHECK-LABEL: module
module {
  // CHECK-LABEL: func @main

    // only test one combination
    @RequiredFeature(feature=GradleMetadataResolveRunner.REPOSITORY_TYPE, value="ivy")
    def "maven module is not affected by rule requiring ivy module descriptor input"() {
        def mavenModule = mavenRepo.module("org.utils", "api", "1.1").publishWithChangedContent()

        buildFile << """
            configurations { conf }
            repositories {

      <entry name="!?*.java"/>
      <entry name="!?*.fooBar"/>
    </wildcardResourcePatterns>
  </component>
  <component name="ProjectModuleManager">
    <modules>
      <module fileurl="file://$PROJECT_DIR$/root.iml" filepath="$PROJECT_DIR$/root.iml"/>
    </modules>
  </component>

            model(IdeaProject).withArguments('--include-build', 'buildB').get()
        }.modules[0]

        then:
        ideaModule.dependencies.size() == 1
        with(ideaModule.dependencies.first()) {
            it instanceof IdeaModuleDependency
            targetModuleName == "b1"
        }
    }

    def "Idea model honours custom module name"() {
        when:
        buildB.buildFile << """