* limitations under the License.
 */

package gradlebuild.basics

import org.gradle.api.artifacts.dsl.RepositoryHandler


fun RepositoryHandler.googleApisJs() {
    ivy {
        name = "googleApisJs"
        setUrl("https://ajax.googleapis.com/ajax/libs")
        patternLayout {
            artifact("[organization]/[revision]/[module].[ext]")
            ivy("[organization]/[revision]/[module].xml")
        }

          results_format: sarif
          publish_results: true

      # Upload the results as artifacts (optional). Commenting out will disable uploads of run results in SARIF
      # format to the repository Actions tab.
      - name: "Upload artifact"
        uses: actions/upload-artifact@b7c566a772e6b6bfb58ed0dc250532a479d7789f # v6.0.0
        with:
          name: SARIF file
          path: results.sarif

 * or similar ad-hoc collections of artifacts. This repository is considered read-only
 * within the context of a session, meaning it can only be used for artifact resolution,
 * not for installation or deployment. This interface does not provide direct access
 * to artifacts; that functionality is handled by a {@code WorkspaceReader}.
 */

     * could serve as a classpath for a particular scope
     *
     * @param dirtyGraph - dependency graph
     * @param scope - which classpath to extract
     * @param resolve - whether to resolve artifacts.
     * @return Collection of metadata objects in the linked subgraph of the graph which
     *             contains the graph.getEntry() vertice
     */

  // For now, we'll keep the standard ones and allow modules to add more
  androidSignature(library("signature-android-apilevel21")) { artifact { type = "signature" } }
  jvmSignature(library("codehaus-signature-java18")) { artifact { type = "signature" } }

  "lintChecks"(library("androidx-lint-gradle"))
}

configure<com.android.build.api.dsl.Lint> {
  xmlReport = true
  checkDependencies = true

/**
 * Service provider interface for registering custom {@link Type} implementations.
 * <p>
 * This interface allows plugins and extensions to define and register additional artifact types
 * beyond the standard ones provided by Maven (like jar, war, pom, etc.). Types define how artifacts
 * are handled, including their default extension, classifier, and language.
 * <p>

Guillaume Nodet <******@****.***> 1729859506 +0200

In the elasticsearch codebase we have test fixtures and actual tests within the same sourceSet. Therefore we introduced the `elasticsearch.internal-test-artifact` plugin to provides another build artifact of your project based on the `test` sourceSet.


This artifact can be resolved by the consumer project as shown in the example below:

```
dependencies {

For debugging purposes we also need to keep track of what versions of artifacts are being used so that when we are debugging in the IDE we can find the specific sources for a given version of a library so that the developer can debug the correct version of a library being used for a plugin.

h3. Discovery all Plexus components

 * failing tasks only, to not use up unnecessary disk space on Team City. This also improves the performance of
 * artifact publishing by reducing the artifacts and packaging reports that consist of multiple files.
 *
 * Reducing the number of reports also makes it easier to find the important ones when analysing a failed build in
 * TeamCity.
 */