This directory contains templates that work around gradle-ospackage-plugin
trying to be helpful and adding templates for your os packaging scripts. We
have relatively nice scripts already so we just override the templates to be

 *
 * <p>Multimaps are commonly used in places where a {@code Map<K, Collection<V>>} would otherwise
 * have appeared. The differences include:
 *
 * <ul>
 *   <li>There is no need to populate an empty collection before adding an entry with {@link #put
 *       put}.
 *   <li>{@code get} never returns {@code null}, only an empty collection.
 *   <li>A key is contained in the multimap if and only if it maps to at least one value. Any

    @Test
    public void testAddInitialSettings() {
        // Test adding single setting
        SuggestSettingsBuilder result = builder.addInitialSettings("key1", "value1");
        assertEquals(builder, result); // Test method chaining
        assertEquals(1, builder.initialSettings.size());
        assertEquals("value1", builder.initialSettings.get("key1"));

        // Test adding multiple settings
        builder.addInitialSettings("key2", 100);

In that case, they will be applied to all the *path operations* in the application:

{* ../../docs_src/dependencies/tutorial012_an_py310.py hl[17] *}


And all the ideas in the section about [adding `dependencies` to the *path operation decorators*](dependencies-in-path-operation-decorators.md) still apply, but in this case, to all of the *path operations* in the app.

    if (FORBIDDEN_DEPENDENCIES.contains(artifactName)) {
      throw new GradleException("Dependency '${artifactName}' on configuration '${configuration.name}' is not allowed. " +
        "If it is needed as a transitive depenency, try adding it to the runtime classpath")
    }
  }
}

subprojects {
  if (project.path.startsWith(':test:fixtures:') || project.path.equals(':build-tools')) {
    // fixtures are allowed to use whatever dependencies they want...

n.com/blogs/storage/replicating-existing-objects-between-s3-buckets/) can be enabled by passing `existing-objects` as a value to `--replicate` flag while adding or editing a replication rule.

Once existing object replication is enabled, all objects or object prefixes that satisfy the replication rules and were created prior to adding replication configuration OR while replication rules were disabled will be synced to the target cluster. Depending on the number of previously existing objects,...

     */
    public static Duration elapsed() {
        return get().elapsedTime();
    }

    /**
     * Returns a monotonically increasing instant.
     * <p>
     * The returned instant is calculated by adding the elapsed nanoseconds
     * since clock creation to the initial wall clock time. This ensures that
     * the time never goes backwards and maintains a consistent relationship
     * with the wall clock time.
     *

        String coreTest = "foo/10_basic.yml"
        String xpackTest = "bar/10_basic.yml"
        setupRestResources([apiCore1, apiCore2, apiXpack], [coreTest], [xpackTest])
        // intentionally not adding tests to project, they will be copied over via the plugin
        // this tests that the test copy happens before the api copy since the api copy will only trigger if there are tests in the project

        when:

import org.apache.maven.api.annotations.Experimental;
import org.apache.maven.api.cli.Options;

/**
 * Defines the options specific to the Maven Shell tool.
 * This interface extends the general {@link Options} interface, adding shell-specific configuration options.
 *
 * @since 4.0.0
 */
@Experimental

1.  Make sure the Issue Template is filled out.
1.  The issue should be related to the repo it is created in.

**Here's why we have this policy:** We want to focus on the work that benefits
the whole community, e.g., fixing bugs and adding features. Individual support
should be sought on Stack Overflow or other non-GitHub channels. It helps us to