META-INF/MANIFEST.MF Manifest-Version: 1.0 Implementation-Title: maven-wrapper Implementation-Version: 0.5.6 Archiver-Version: Provisio Archiver Built-By: manfred Specification-Title: maven-wrapper Implementation-Vendor-Id: io.takari Created-By: Takari Inc. Build-Jdk: 1.8.0_232 Specification-Version: 0.5.6 META-INF/maven/io.takari/maven-wrapper/pom.properties version=0.5.6 groupId=io.takari artifactId=maven-wrapper org/apache/maven/wrapper/BootstrapMainStarter.class package org.apache.maven.wrapper;...

META-INF/MANIFEST.MF Manifest-Version: 1.0 Archiver-Version: Plexus Archiver Created-By: Apache Maven Built-By: BEBE Build-Jdk: 1.6.0_07 META-INF/maven/plugin.xml A test plugin to assist testing of Maven core. org.apache.maven.its.plugins maven-it-plugin 0.1 it false true generate-metadata Does nothing. compile false true false false false true process-classes org.apache.maven.plugin.coreit.DMojo java per-lookup once-per-session java Does nothing. false true false false false true generate-sources...

/// info

This requires installing `ujson` for example with `pip install ujson`.

///

/// warning

`ujson` is less careful than Python's built-in implementation in how it handles some edge-cases.

///

{* ../../docs_src/custom_response/tutorial001_py39.py hl[2,7] *}

/// tip

It's possible that `ORJSONResponse` might be a faster alternative.

     * where resource {@code targetPath} elements were always interpreted as relative to the output directory
     * ({@code project.build.outputDirectory} or {@code project.build.testOutputDirectory}),
     * not the project base directory. Maven 3 plugins (like maven-resources-plugin) expect to receive
     * the relative path and perform the resolution themselves.
     * </p>

- Kubernetes is now built using go1.15.2
  - build: Update to k/repo-infra@v0.1.1 (supports go1.15.2)
  - build: Use go-runner:buster-v2.0.1 (built using go1.15.1)
  - bazel: Replace --features with Starlark build settings flag
  - hack/lib/util.sh: some bash cleanups
    
    - switched one spot to use kube::logging

simultaneously - progress of the syncing can be monitored by looking at `mc replicate resync status alias/bucket --remote-bucket <arn>`. In the event that resync operation failed to replicate some versions, they would be picked up by the healing mechanism in-built as part of the scanner. If the resync operation reports a failed status or in the event of a cluster restart while resync is in progress, a fresh `resync start` can be issued - this will replicate previously unsynced content at the cost of additional...

     */
    @Nonnull
    Model getModel();

    /**
     * Shorthand method.
     *
     * @return the build element of the project model
     */
    @Nonnull
    default Build getBuild() {
        Build build = getModel().getBuild();
        return build != null ? build : Build.newInstance();
    }

    /**
     * Returns the path to the pom file for this project.

 * create an instance of one of the built-in implementations of {@code Graph}, use the {@link
 * GraphBuilder} class:
 *
 * {@snippet :
 * MutableGraph<Integer> graph = GraphBuilder.undirected().build();
 * }
 *
 * <p>{@link GraphBuilder#build()} returns an instance of {@link MutableGraph}, which is a subtype

 * create an instance of one of the built-in implementations of {@code Graph}, use the {@link
 * GraphBuilder} class:
 *
 * {@snippet :
 * MutableGraph<Integer> graph = GraphBuilder.undirected().build();
 * }
 *
 * <p>{@link GraphBuilder#build()} returns an instance of {@link MutableGraph}, which is a subtype

    assertEquals(0x330000, (int) webSafeColorArray[36]);
    ImmutableSet<Integer> addedColor = webSafeColorsBuilder.add(LAST_COLOR_ADDED).build();
    assertEquals(
        "Modifying the builder should not have changed any already built sets",
        216,
        webSafeColors.size());
    assertEquals("the new array should be one bigger than webSafeColors", 217, addedColor.size());