Search Options

Results per page
Sort
Preferred Languages
Advance

Results 391 - 400 of 667 for Want (0.62 sec)

  1. compat/maven-compat/src/main/java/org/apache/maven/repository/legacy/resolver/DefaultLegacyArtifactCollector.java

            Artifact managedOriginatingArtifact = versionMap.get(originatingArtifact.getDependencyConflictId());
    
            if (managedOriginatingArtifact != null) {
                // TODO we probably want to warn the user that he is building an artifact with
                // different values than in dependencyManagement
                if (managedVersions instanceof ManagedVersionMap) {
    Registered: Sun Dec 28 03:35:09 UTC 2025
    - Last Modified: Fri Jun 06 14:28:57 UTC 2025
    - 36.5K bytes
    - Viewed (0)
  2. helm-releases/minio-4.0.15.tgz

    version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. ### Configuration...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Wed Sep 21 11:07:01 UTC 2022
    - 20K bytes
    - Viewed (0)
  3. helm-releases/minio-4.0.11.tgz

    version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. ### Configuration...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Sun Aug 07 05:41:47 UTC 2022
    - 19.2K bytes
    - Viewed (0)
  4. helm-releases/minio-4.0.2.tgz

    version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. ### Configuration...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Mon May 09 04:25:47 UTC 2022
    - 18K bytes
    - Viewed (0)
  5. helm-releases/minio-4.0.3.tgz

    version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. ### Configuration...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Fri Jul 08 06:16:22 UTC 2022
    - 18K bytes
    - Viewed (0)
  6. helm-releases/minio-5.0.0.tgz

    version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. ### Configuration...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Tue Oct 25 10:20:22 UTC 2022
    - 19.8K bytes
    - Viewed (0)
  7. docs/en/docs/deployment/manually.md

    These examples run the server program (e.g Uvicorn), starting **a single process**, listening on all the IPs (`0.0.0.0`) on a predefined port (e.g. `80`).
    
    This is the basic idea. But you will probably want to take care of some additional things, like:
    
    * Security - HTTPS
    * Running on startup
    * Restarts
    * Replication (the number of processes running)
    * Memory
    * Previous steps before starting
    
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Sat Oct 11 17:48:49 UTC 2025
    - 6.9K bytes
    - Viewed (0)
  8. compat/maven-compat/src/test/java/org/apache/maven/AbstractCoreMavenComponentTestCase.java

            }
    
            return request;
        }
    
        // layer the creation of a project builder configuration with a request, but this will need to be
        // a Maven subclass because we don't want to couple maven to the project builder which we need to
        // separate.
        protected MavenSession createMavenSession(File pom) throws Exception {
            return createMavenSession(pom, new Properties());
        }
    
    Registered: Sun Dec 28 03:35:09 UTC 2025
    - Last Modified: Fri Jan 24 17:29:44 UTC 2025
    - 12.1K bytes
    - Viewed (0)
  9. src/bytes/compare_test.go

    		for offset := 0; offset <= numShifts; offset++ {
    			shiftedB := buffer[offset : len(tt.b)+offset]
    			copy(shiftedB, tt.b)
    			cmp := Compare(tt.a, shiftedB)
    			if cmp != tt.i {
    				t.Errorf(`Compare(%q, %q), offset %d = %v; want %v`, tt.a, tt.b, offset, cmp, tt.i)
    			}
    		}
    	}
    }
    
    func TestCompareIdenticalSlice(t *testing.T) {
    	var b = []byte("Hello Gophers!")
    	if Compare(b, b) != 0 {
    		t.Error("b != b")
    	}
    Registered: Tue Dec 30 11:13:12 UTC 2025
    - Last Modified: Thu Jul 13 23:11:42 UTC 2023
    - 6.8K bytes
    - Viewed (0)
  10. helm-releases/minio-3.0.0.tgz

    version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. Configuration ----------...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Thu Sep 02 01:47:43 UTC 2021
    - 13.8K bytes
    - Viewed (0)
Back to top