<jsp-config>
    <jsp-property-group>
      <url-pattern>*.jsp</url-pattern>
      <el-ignored>false</el-ignored>
      <page-encoding>UTF-8</page-encoding>
      <scripting-invalid>false</scripting-invalid>
      <include-prelude>/WEB-INF/view/common/common.jsp</include-prelude>
    </jsp-property-group>
  </jsp-config>

            "Infra/Core",
            "Infra/Logging",
            "Infra/Node Lifecycle",
            "Infra/Plugins",
            "Infra/REST API",
            "Infra/Resiliency",
            "Infra/Scripting",
            "Infra/Settings",
            "Infra/Transport API",
            "License",
            "Machine Learning",
            "Mapping",
            "Network",
            "Packaging",

        List<RelatedQuery> testData = new ArrayList<>();
        testData.add(createRelatedQuery("java", new String[] { "programming", "tutorial" }, ""));
        testData.add(createRelatedQuery("python", new String[] { "scripting", "data science" }, ""));
        mockBhv.setTestData(testData);

        int count = relatedQueryHelper.load();
        assertEquals(1, count); // One virtual host key (empty)

  Returns:
    boolean value of the variable.

  Raises:
    UserInputError: if an environment variable is set, but it cannot be
      interpreted as a boolean indicator, assume that the user has made a
      scripting error, and will continue to provide invalid input.
      Raise the error to avoid infinitely looping.
  """
  if not question:
    question = 'Do you wish to build TensorFlow with {} support?'.format(

- we also seem to have information like the plugin lifecycle model that's buried inside the maven execution model
- we also seem to have artifact information tangled inside the plugin model
- we have to deal with scripting implementations (groovy, beanshell, ruby)
- we need to deal with a shared context for plugins, like the guarded mojos
- we need to deal with plugins as core application logic which can also interact with plugins

					<groupId>org.opensearch.plugin</groupId>
					<artifactId>analysis-common</artifactId>
				</exclusion>
				<exclusion>
					<groupId>org.opensearch.plugin</groupId>
					<artifactId>opensearch-scripting-painless-spi</artifactId>
				</exclusion>
				<exclusion>
					<groupId>org.opensearch.plugin</groupId>
					<artifactId>geo</artifactId>
				</exclusion>
			</exclusions>
		</dependency>

    }

    @Test
    public void test_searchWithQuery_allows_scriptKeyword() {
        chatClient.resetSearchDocumentsCalled();
        chatClient.testSearchWithQuery("painless scripting tutorial");
        assertTrue(chatClient.wasSearchDocumentsCalled());
    }

    @Test
    public void test_searchWithQuery_allows_internalFieldName() {
        chatClient.resetSearchDocumentsCalled();

                }
            });

            // TODO: remove this once ctx isn't added to update script params in 7.0
            test.systemProperty("es.scripting.update.ctx_in_params", "false");

            // TODO: remove this property in 8.0
            test.systemProperty("es.search.rewrite_sort", "true");

          <description>
            <![CDATA[
            Specifies the language of the source files - typically {@code java} or {@code resources}.
            Resources is used as a generic term for scripting languages (e.g., JavaScript or Python)
            or markup languages (e.g. properties file, <abbr>JSON</abbr> or <abbr>XML</abbr>).

        this.requestCacheSize = requestCacheSize;
    }

    /**
     * Sets the script language.
     * @param scriptLang The script language.
     */
    public void setScriptLang(final String scriptLang) {
        this.scriptLang = scriptLang;
    }

    /**
     * Sets the script code.
     * @param scriptCode The script code.
     */