/// tip

You could use the same technique to extend the JSON Schema and add your own custom extra info.

For example you could use it to add metadata for a frontend user interface, etc.

///

/// info

        File baseDirectory = new File(args[0]);
        System.out.println("- Using base directory: " + baseDirectory.getAbsolutePath());

        // If the maven-wrapper.properties exists, read it and check if it contains a custom
        // wrapperUrl parameter.
        File mavenWrapperPropertyFile = new File(baseDirectory, MAVEN_WRAPPER_PROPERTIES_PATH);
        String url = DEFAULT_DOWNLOAD_URL;
        if(mavenWrapperPropertyFile.exists()) {

second intervals between attempts $MC_COMMAND ; STATUS=$? ; done ; set -e ; # reset `e` as active return 0 } # runCommand ($@) # Run custom mc command runCommand() { ${MC} "$@" return $? } # Try connecting to MinIO instance {{- if .Values.tls.enabled }} scheme=https {{- else }} scheme=http {{- end }} connectToMinio $scheme {{ if .Values.customCommands }} # Run custom commands {{- range .Values.customCommands }} runCommand {{ .command }} {{- end }} {{- end }} minio/templates/_helper_policy.tpl {{-...

second intervals between attempts $MC_COMMAND ; STATUS=$? ; done ; set -e ; # reset `e` as active return 0 } # runCommand ($@) # Run custom mc command runCommand() { ${MC} "$@" return $? } # Try connecting to MinIO instance {{- if .Values.tls.enabled }} scheme=https {{- else }} scheme=http {{- end }} connectToMinio $scheme {{ if .Values.customCommands }} # Run custom commands {{- range .Values.customCommands }} runCommand {{ .command }} {{- end }} {{- end }} minio/templates/_helper_policy.tpl {{-...

second intervals between attempts $MC_COMMAND ; STATUS=$? ; done ; set -e ; # reset `e` as active return 0 } # runCommand ($@) # Run custom mc command runCommand() { ${MC} "$@" return $? } # Try connecting to MinIO instance {{- if .Values.tls.enabled }} scheme=https {{- else }} scheme=http {{- end }} connectToMinio $scheme {{ if .Values.customCommands }} # Run custom commands {{- range .Values.customCommands }} runCommand {{ .command }} {{- end }} {{- end }} minio/templates/_helper_policy.tpl {{-...

   *       visible static factory method whose return type is {@code C} or {@code C}'s subtype.
   * </ul>
   *
   * <p>In all cases, if {@code C} needs custom logic for testing serialization, you can add an
   * explicit {@code testSerializable()} test in the corresponding {@code CTest} class, and {@code
   * C} will be excluded from automated serialization test performed by this method.

When configured, MinIO sends request and credential details for every API call to an external HTTP(S) endpoint and expects an allow/deny response. MinIO is thus able to delegate access management to an external system, and users are able to use a custom solution instead of S3 standard IAM policies.

.Values.configPathmc }}certs {{ end }} resources: {{ toYaml .Values.makeUserJob.resources | indent 10 }} {{- end }} minio/templates/post-install-custom-command.yaml {{- if .Values.customCommands }} apiVersion: batch/v1 kind: Job metadata: name: {{ template "minio.fullname" . }}-custom-command-job namespace: {{ .Release.Namespace | quote }} labels: app: {{ template "minio.name" . }}-custom-command-job chart: {{ template "minio.chart" . }} release: {{ .Release.Name }} heritage: {{ .Release.Service }} annotations: "helm.sh/hook":...

.Values.configPathmc }}certs {{ end }} resources: {{ toYaml .Values.makeUserJob.resources | indent 10 }} {{- end }} minio/templates/post-install-custom-command.yaml {{- if .Values.customCommands }} apiVersion: batch/v1 kind: Job metadata: name: {{ template "minio.fullname" . }}-custom-command-job namespace: {{ .Release.Namespace | quote }} labels: app: {{ template "minio.name" . }}-custom-command-job chart: {{ template "minio.chart" . }} release: {{ .Release.Name }} heritage: {{ .Release.Service }} annotations: "helm.sh/hook":...

 * Google-internal Android suite generators. Note that those generators also suppress any test
 * annotated with LargeTest.
 *
 * <p>Why use a custom annotation instead of {@code android.test.suitebuilder.annotation.Suppress}?
 * I'm not completely sure that this is the right choice, but it has various advantages:
 *
 * <ul>