Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 4 of 4 for 410 (0.03 sec)

  1. src/cmd/go/testdata/script/mod_proxy_list.txt

    env GOPROXY=$proxy/500|https://0.0.0.0|$proxy
    go get rsc.io/quote@v1.3.0
    
    # get should return the final error if that's all we have.
    env GOPROXY=$proxy/404,$proxy/410
    ! go get rsc.io/quote@v1.4.0
    stderr 'reading.*/410/rsc.io/.*: 410 Gone'
    
    -- go.mod --
    Registered: Wed Jun 12 16:32:35 UTC 2024
    - Last Modified: Tue Sep 28 17:19:14 UTC 2021
    - 1.1K bytes
    - Viewed (0)
  2. platforms/core-configuration/kotlin-dsl/src/main/kotlin/org/gradle/kotlin/dsl/assignment/internal/KotlinDslAssignment.kt

    
    /**
     * This class is used in `kotlin-dsl` plugin from 4.0.2 to 4.1.0. To be removed in Gradle 9.0.
     */
    @Suppress("unused")
    object KotlinDslAssignment {
    
        init {
            DeprecationLogger.deprecate("Internal class ${KotlinDslAssignment::class.java.name}")
    Registered: Wed Jun 12 18:38:38 UTC 2024
    - Last Modified: Wed Aug 02 08:06:49 UTC 2023
    - 1.3K bytes
    - Viewed (0)
  3. src/cmd/go/testdata/script/mod_list_update_nolatest.txt

    # We use a local file proxy, since our test proxy doesn't have the behavior
    # we want to test, and we don't want it to be too clever.
    # Verifies #45305, where proxy.golang.org serves an empty /@v/list (200)
    # but has no /@latest (410) because the go.mod at the tip of the default
    # branch has a different major version suffix.
    env testproxy=$GOPROXY
    env GOPROXY=file:///$WORK/proxy
    env GOSUMDB=off
    
    # If the proxy does not return a list of versions (404/410)
    Registered: Wed Jun 12 16:32:35 UTC 2024
    - Last Modified: Wed Sep 15 00:06:54 UTC 2021
    - 2K bytes
    - Viewed (0)
  4. maven-core/src/site/apt/inheritance.apt

      maven occur, the maven inheritance model must be pinned against a particular
      modelVersion. This is required so that a change from modelVersion 4.0.0 to
      4.1.0 doesn't cause compatibility problems with users who have not upgraded
      their projects. It also allows for a certain amount of legacy support into the
      future. Therefore, we should rename this file from pom.xml in the maven-core
    Registered: Wed Jun 12 09:55:16 UTC 2024
    - Last Modified: Mon Jul 18 17:22:19 UTC 2022
    - 3.5K bytes
    - Viewed (0)
Back to top