licensing terms of the Project Developments that will always supersede such
Code of Conduct.

## Scope

This Code of Conduct applies both within project spaces and in public spaces
when an individual is representing the project or its community. Examples of
representing a project or community include using an official project e-mail

    description: "Testing of the Elasticsearch %BRANCH% branch packaging tests.\n"
    project-type: multijob
    node: master
    vault: []
    scm:
      - git:
          wipe-workspace: false
    builders:
      - multijob:
          name: Packaging tests
          projects:
            - name: elastic+elasticsearch+%BRANCH%+multijob+packaging-tests-unix
              kill-phase-on: NEVER

Unlike many projects on GitHub, the Go project does not use its bug tracker for general discussion or asking questions.
We only use our bug tracker for tracking bugs and tracking proposals going through the [Proposal Process](https://go.dev/s/proposal-process).

For asking questions, see:

* [The golang-nuts mailing list](https://groups.google.com/d/forum/golang-nuts)

* [The Go Forum](https://forum.golangbridge.org/), a web-based forum

     * provided, the generated location will omit the model id and source information and only give line/column
     * information for problems originating directly from this POM.
     *
     * @param problem The problem whose location should be formatted, must not be {@code null}.

## Structure

Each platform and module has its own source directory under [platforms/](../platforms).
In these source directories, you will find the Gradle projects that make up the platform or module.

The platforms and modules are defined using a DSL in [settings.gradle.kts](../settings.gradle.kts)

":"on","name":"","description":"","expiration":"1970-01-01T00:00:00Z"},"dillon-svcacct-1":{"parent":"uid=dillon,ou=people,ou=swengg,dc=min,dc=io","accessKey":"dillon-svcacct-1","secretKey":"dillon-svcacct-1","groups":["cn=projecta,ou=groups,ou=swengg,dc=min,dc=io","cn=projectb,ou=groups,ou=swengg,dc=min,dc=io"],"claims":{"accessKey":"dillon-svcacct-1","ldapActualUser":"uid=dillon,ou=people,ou=swengg,dc=min,dc=io","ldapUser":"uid=dillon,ou=people,ou=swengg,dc=min,dc=io","ldapUsername":"dillon","p...

     */
    @Nonnull
    Optional<Path> getPath();

    /**
     * Gets the source of the project to build.
     * This is an alternative to specifying a path, allowing the project to be built from
     * a model source such as a string or input stream.
     *
     * @return an optional containing the source of the project, or empty if not specified
     */

   questions. Those who are asked should be responsive and helpful.

 * **Step down considerately**: Members of every project come and go. When somebody leaves or
   disengages from the project, they should make it known and take the proper steps to ensure that
   others can pick up where they left off.

 *
 * <p>This package contains interfaces and classes for the Maven upgrade tool,
 * which provides functionality for upgrading Maven projects and dependencies.</p>
 *
 * <p>Key features include:</p>
 * <ul>
 *   <li>Project upgrade capabilities</li>
 *   <li>Dependency version management</li>
 *   <li>Configuration migration</li>
 *   <li>Interactive upgrade workflows</li>
 * </ul>
 *

import java.util.function.Function;
import java.util.stream.Collectors;

import static org.elasticsearch.gradle.util.GradleUtils.getProjectPathFromTask;

/**
 * Copies the files needed for the Rest YAML specs to the current projects test resources output directory.
 * This is intended to be be used from {@link RestResourcesPlugin} since the plugin wires up the needed
 * configurations and custom extensions.
 *
 * @see RestResourcesPlugin
 */