github-hooks: true
          status-context: elasticsearch-ci/packaging-tests-unix
          cancel-builds-on-update: true
          black-list-target-branches:
            - 6.8
          excluded-regions:
            - ^docs/.*
          white-list-labels:
            - ':Delivery/Packaging'
          black-list-labels:
            - '>test-mute'
    axes:
      - axis:
          type: label-expression

          github-hooks: true
          status-context: elasticsearch-ci/packaging-tests-windows-sample
          cancel-builds-on-update: true
          white-list-target-branches:
            - master
          excluded-regions:
            - ^docs/.*
          black-list-labels:
            - '>test-mute'
            - ':Delivery/Packaging'
    axes:
      - axis:
          type: label-expression
          name: os

        #
        #; objectTypeTargetList = list:{TABLE ; VIEW}

        # o tableExceptList: (NotRequired - Default list:{})
        #  If you want to exclude some tables in generating target,
        #  you should specify the list of excepted table hints.
        #    e.g. list:{PRODUCT_STATUS ; prefix:TMP_}
        #  This is only for the main schema. Additional schemas are unconcerned.

     * @param freqField The frequency field name
     * @param kindToRemove The kind to remove
     * @param freqSetter The consumer to set frequency to 0
     * @param excludeKinds The kinds to exclude from deletion
     * @return The SuggestDeleteResponse
     */
    public SuggestDeleteResponse deleteWordsByKind(final String index, final String freqField, final SuggestItem.Kind kindToRemove,

 * under the License.
 */
package org.apache.maven.artifact.resolver.filter;

import java.util.List;

import org.apache.maven.artifact.Artifact;

/**
 * Filter to exclude from a list of artifact patterns.
 *
 * TODO I think this is equiv. to exclusion set filter in maven-core
 */
public class ExcludesArtifactFilter extends IncludesArtifactFilter {

          cancel-builds-on-update: true
          # We've removed the no-jdk distribution on master as well
          black-list-target-branches:
            - master
            - 6.8
          excluded-regions:
            - ^docs/.*
          black-list-labels:
            - '>test-mute'
            - ':Delivery/Packaging'
    axes:
      - axis:
          type: label-expression
          name: os

     * @return HTML response for the search results
     */
    @Execute
    @Secured({ ROLE, ROLE + VIEW })
    public HtmlResponse search(final SearchForm form) {
        copyBeanToBean(form, labelTypePager, op -> op.exclude(Constants.PAGER_CONVERSION_RULE));
        return asHtml(path_AdminLabeltype_AdminLabeltypeJsp).renderWith(data -> {
            searchPaging(data, form);
        });
    }

    /**

          github-hooks: true
          status-context: elasticsearch-ci/packaging-tests-unix-sample
          cancel-builds-on-update: true
          black-list-target-branches:
            - 6.8
          excluded-regions:
            - ^docs/.*
          black-list-labels:
            - '>test-mute'
            - ':Delivery/Packaging'
    axes:
      - axis:
          type: label-expression
          name: os

          github-hooks: true
          status-context: elasticsearch-ci/part-1-windows
          cancel-builds-on-update: true
          black-list-target-branches:
            - 6.8
          excluded-regions:
            - ^docs/.*
          white-list-labels:
            - 'test-windows'
          black-list-labels:
            - '>test-mute'
    builders:
      - inject:

<module>
<source path="">
  <!-- Hack to keep collect from hiding collect.testing supersource: -->
  <exclude name="**/testing/**"/>
</source>

<!--
    We used to set this only for packages that had manual supersource. That
    worked everywhere that I know of except for one place: when running the GWT
    util.concurrent tests under Guava.

    The problem is that GWT responds poorly to two .gwt.xml files in the same
    Java package; see