plugins {
    kotlin("jvm")
    id("jps-compatible")
}

dependencies {
    api(project(":compiler:psi"))
    api(project(":analysis:analysis-api-platform-interface"))
    api(project(":analysis:project-structure"))
    api(intellijCore())

    testApi(platform(libs.junit.bom))
    testImplementation(libs.junit.jupiter.api)
    testRuntimeOnly(libs.junit.jupiter.engine)
    testImplementation(kotlinTest("junit"))

# Checks that source debug information is used in the output error message.
# CHECK: error: 'tf.Add' op operands don't have broadcast-compatible shapes
# CHECK: math_ops.add(x, y, name='x_y_sum')
# CHECK: build_graph(out_dir)
node: {
  name: "x"
  op: "Placeholder"
  attr: {
    key: "shape"
    value: {
      shape: {
        dim: {

}

// tag::copy[]
tasks.register<Copy>("copyFiles") {
    into(layout.buildDirectory.dir("output"))
    // Store the configuration into a variable because referencing the project from the task action
    // is not compatible with the configuration cache.
    val compileClasspath: FileCollection = configurations.compileClasspath.get()
    from(compileClasspath)
    doFirst {

# - istioctl
# - documentation
area: istioctl

# releaseNotes is a markdown listing of any user facing changes. This will appear in the
# release notes.
releaseNotes:
  - |

  This reduces the permissions required in the gateways, improves performance, and will make certificate reading
  more flexible in the future. This change is fully backwards compatible with the old method, and requires no changes
  to your cluster. If required, it can be disabled by setting the `ISTIOD_ENABLE_SDS_SERVER=false`

    | org.gradle.jvm.environment     |          | standard-jvm |
    | org.gradle.jvm.version         |          | 11           |
   Selection reasons:
      - Was requested: we require a JDK 9 compatible bytecode generator

org.ow2.asm:asm:7.1
\--- compileClasspath

Currently, the Gradle model for Platform does not allow us to differentiate between different c-runtime, ABI or other binary variants.
This means that it is not possible to differentiate between a prebuilt library binary compatible with VS2010 vs VS2013.

As such, this sample will only work without modification on Windows with Visual Studio 2010. Uncomment the relevant line in the

<%@page pageEncoding="UTF-8" contentType="text/html; charset=UTF-8"%>
<meta content='width=device-width, initial-scale=1, maximum-scale=1, user-scalable=no' name='viewport'>
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<link href="${fe:url('/css/admin/bootstrap.min.css')}" rel="stylesheet" type="text/css" />
<link href="${fe:url('/css/admin/font-awesome.min.css')}" rel="stylesheet" type="text/css" />

Currently, the Gradle model for Platform does not allow us to differentiate between different c-runtime, ABI or other binary variants.
This means that it is not possible to differentiate between a prebuilt library binary compatible with VS2010 vs VS2013.

As such, this sample will only work without modification on Windows with Visual Studio 2010. Uncomment the relevant line in the

import java.lang.String;
import java.util.List;
import java.util.Arrays;

/**
 * This is the implementation of the custom tooling model. It must be serializable and must have methods and properties that
 * are compatible with the custom tooling model interface. It may or may not implement the custom tooling model interface.
 */
public class DefaultModel implements Serializable {
    public String getName() {
        return "name";
    }