},
  {
    "name": "ide",
    "path": "platforms/ide/ide",
    "unitTests": true,
    "functionalTests": true,
    "crossVersionTests": false
  },
  {
    "name": "ide-native",
    "path": "platforms/ide/ide-native",
    "unitTests": true,
    "functionalTests": true,
    "crossVersionTests": false
  },
  {
    "name": "ide-plugins",
    "path": "platforms/ide/ide-plugins",

# Native
platforms/native/                 @gradle/bt-jvm

# IDE Experience
platforms/ide/                    @gradle/bt-tide
# Eventually be moved to the core platform.
# Currently heavily developed by the bt-ide-experience team.
platforms/ide/problems/           @gradle/bt-tide
platforms/ide/ide-native/         @gradle/bt-tide @gradle/bt-jvm

# Documentation

        name = "Smoke Ide Tests$suffix"
        description = "Tests against IDE sync process"

        requirements {
            // These tests are usually heavy and the build time is twice on EC2 agents
            requiresNotEc2Agent()
        }

        applyTestDefaults(
            model = model,
            buildType = this,
            gradleTasks = ":smoke-ide-test:smokeIdeTest",

            <option value="$PROJECT_DIR$/platforms/ide/base-ide-plugins" />
            <option value="$PROJECT_DIR$/platforms/ide/ide" />
            <option value="$PROJECT_DIR$/platforms/ide/ide-native" />
            <option value="$PROJECT_DIR$/platforms/ide/ide-plugins" />
            <option value="$PROJECT_DIR$/platforms/ide/problems" />
            <option value="$PROJECT_DIR$/platforms/ide/problems-api" />

            includeModule("org.gradle.buildtool.internal", "configuration-cache-report")
            includeModule("org.gradle.buildtool.internal", "gradle-ide-starter")
            includeModule("org.gradle.buildtool.internal", "gradle-ide-starter-scenarios")
        }
    }
    google {
        content {
            includeGroup("com.android.databinding")

Our codebase uses `null` extensively to represent an absence of value or optionality of the argument.
We utilize nullness annotations in Java code and somewhat rely on IDE warnings to guide us.
However, the Java code we have is not fully annotated, which causes several consequences:
* IDE warnings can be misleading
* Redundant null checks may increase binary size, hurt performance, and increase cognitive load for readers

 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */

package gradlebuild.integrationtests.ide

import gradlebuild.basics.BuildEnvironment
import gradlebuild.basics.androidStudioHome
import gradlebuild.basics.autoDownloadAndroidStudio
import gradlebuild.basics.runAndroidStudioInHeadlessMode

### Setup for OpenSearch Plugins

Run antrun:run to download plugins into the plugins directory:

    $ mvn antrun:run

### Run Fess

Run or debug org.codelibs.fess.FessBoot on your IDE, and then access http://localhost:8080/

### Build Package

/*/*/*/*/*.iml
/out
/*/out
/*/*/out
/*/*/*/out
/*/*/*/*/out
/.teamcity/target
/gradle.ipr
/gradle.iws

# Eclipse
# -------
*.classpath
*.project
*.settings
/bin
/subprojects/*/bin
atlassian-ide-plugin.xml
.metadata/

# NetBeans
# --------
.nb-gradle
.nb-gradle-properties

# Vim
# ---
*.sw[nop]

# Emacs
# -----
*~
\#*\#
.\#*

# Textmate
# --------
.textmate

gradlePlugin {
    plugins {
        register("androidStudioProvisioning") {
            id = "gradlebuild.android-studio-provisioning"
            implementationClass = "gradlebuild.integrationtests.ide.AndroidStudioProvisioningPlugin"
        }
    }

    plugins {
        register("androidHomeWarmup") {
            id = "gradlebuild.android-home-warmup"