# This test illustrates a case where an upgrade–downgrade–upgrade cycle could
# add extraneous dependencies due to another module depending on an
# otherwise-unlisted version (such as a pseudo-version).
#
# This case corresponds to the "downhiddenartifact" test in the mvs package.

# The initial package import graph used in the test looks like:
#
# a --- b
#  \     \
#   \     \
#    c --- d
#
# The module dependency graph initially looks like:

}
// end::use_bom_rule[]
} else {
// tag::use_rule[]
dependencies {
    components.all<JacksonAlignmentRule>()
}
// end::use_rule[]
// tag::enforced_platform[]
dependencies {
    // Forcefully downgrade the virtual Jackson platform to 2.8.9
    implementation(enforcedPlatform("com.fasterxml.jackson:jackson-virtual-platform:2.8.9"))
}
// end::enforced_platform[]
}

// tag::bom-alignment-rule[]

*/

package main

import (
	"fmt"
	"os"
	"time"

	"github.com/blang/semver/v4"
	"k8s.io/klog/v2"
)

// EtcdMigrateCfg provides all configuration required to perform etcd data upgrade/downgrade migrations.
type EtcdMigrateCfg struct {
	binPath           string
	name              string
	initialCluster    string
	port              uint64
	peerListenUrls    string
	peerAdvertiseUrls string

 */
package org.gradle.integtests

import org.gradle.integtests.fixtures.CrossVersionIntegrationSpec

class JavaProjectCrossVersionIntegrationTest extends CrossVersionIntegrationSpec {
    def "can upgrade and downgrade Gradle version used to build Java project"() {
        given:
        buildFile << """
apply plugin: 'java'

task custom(type: org.gradle.CustomTask)
        """

        and:

}
// end::use_bom_rule[]
} else {
// tag::use_rule[]
dependencies {
    components.all(JacksonAlignmentRule)
}
// end::use_rule[]
// tag::enforced_platform[]
dependencies {
    // Forcefully downgrade the virtual Jackson platform to 2.8.9
    implementation enforcedPlatform('com.fasterxml.jackson:jackson-virtual-platform:2.8.9')
}
// end::enforced_platform[]
}

// tag::bom-alignment-rule[]

#
# In particular, if the module that previously provided the package has a
# matching version, but does not itself match the pattern and contains no
# matching packages, we should not change its version. (We should *not* downgrade
# module example.net/split to v0.1.0, despite the fact that
# example.net/split v0.2.0 currently provides the package with the requested path.)
#
# TODO(#27899): Maybe we should resolve the ambiguities by upgrading.

    }
  }

  companion object {
    /**
     * The cipher suite used during TLS connection fallback to indicate a fallback. See
     * https://tools.ietf.org/html/draft-ietf-tls-downgrade-scsv-00
     */
    const val TLS_FALLBACK_SCSV = "TLS_FALLBACK_SCSV"
  }

        succeeds("dependencies", "--configuration", "checkstyle")
        output.contains "com.puppycrawl.tools:checkstyle:"

        when:
        buildFile << """
            dependencies {
                //downgrade version:
                checkstyle "com.puppycrawl.tools:checkstyle:5.5"
            }
        """

        then:
        fails("check")
        failure.assertHasErrorOutput("Name 'class1' must match pattern")

stdout '^rsc.io/quote@v1.5.2$'
! stdout 'rsc.io/quote/v3'
go list -e all
! stdout '^rsc.io/quote$'

# 'go mod tidy' should preserve the requirement on rsc.io/quote but mark it
# indirect. This prevents a downgrade to v1.5.1, which could introduce
# an ambiguity.
go mod tidy
go list -m -f '{{.Path}}@{{.Version}}{{if .Indirect}} indirect{{end}}' all
stdout '^rsc.io/quote@v1.5.2 indirect$'
stdout '^rsc.io/quote/v3@v3.0.0$'

[[sec:strict-version]]
`strictly`::
Any version not matched by this version notation will be excluded.
This is the strongest version declaration.
On a declared dependency, a `strictly` can downgrade a version.
When on a transitive dependency, it will cause dependency resolution to fail if no version acceptable by this clause can be selected.