},
      "filter": {
        "stemmer_en_filter": {
          "type": "stemmer",
          "name": "english"
        },
        "english_override": {
          "type":       "stemmer_override",
          "rules": []
        },
        "possessive_stemmer_en_filter": {
          "type": "stemmer",
          "name": "possessive_english"
        },
        "stopword_en_filter": {
          "type": "stop",

      },
      "filter": {
        "stemmer_en_filter": {
          "type": "stemmer",
          "name": "english"
        },
        "english_override": {
          "type":       "stemmer_override",
          "rules": []
        },
        "possessive_stemmer_en_filter": {
          "type": "stemmer",
          "name": "possessive_english"
        },
        "stopword_en_filter": {
          "type": "stop",

import org.codelibs.core.exception.ClIllegalArgumentException;
import org.junit.Rule;
import org.junit.Test;
import org.junit.rules.ExpectedException;

/**
 * @author higa
 *
 */
public class LoggerTest {

    /**
     * @see org.junit.rules.ExpectedException
     */
    @Rule
    public ExpectedException exception = ExpectedException.none();

jects-between-s3-buckets/) can be enabled by passing `existing-objects` as a value to `--replicate` flag while adding or editing a replication rule.

Once existing object replication is enabled, all objects or object prefixes that satisfy the replication rules and were created prior to adding replication configuration OR while replication rules were disabled will be synced to the target cluster. Depending on the number of previously existing objects, the existing objects that are now eligible...

    }

    /**
     * Delays the crawler while waiting for new URLs to be available.
     * This method calibrates CPU load, checks crawler status, applies
     * interval control rules, and then calls the parent implementation.
     * All operations are wrapped in exception handling to ensure robustness
     * in test and production environments.
     */
    @Override

# OkHttp test platform rules uses optional classes.

 * We put artifacts here to avoid accidentally exposing sensitive information publicly.
 */
const val HIDDEN_ARTIFACT_DESTINATION = ".teamcity/gradle-logs"

fun BuildTypeSettings.setArtifactRules(rules: String) {
    artifactRules = rules
    publishArtifacts = PublishMode.ALWAYS
}

fun BuildType.applyDefaultSettings(
    os: Os = Os.LINUX,
    arch: Arch = Arch.AMD64,
    buildJvm: Jvm = BuildToolBuildJvm,

# proto-file: devtools/build_cleaner/proto/actions.proto
# proto-message: ActionSpecs

# Python rules should not have more than one source file.
action_spec {
  action: CHECK_FILE_COUNT
  file_count_params {
    rule_selector {
      rule_kind_regex: "^.*py(type)?(_strict)?_(binary|library|test).*$"
      generator_function_regex: "^(?!boq_header)$"
    }
    max_source_count: 1
  }

* `org.gradle.experimental.declarative-common` – public property of an unstable feature

## Decision

New properties will adhere to the explicit naming rules, and existing properties will be updated where possible.

The naming rules are user-centric.
By the name alone, users will be able to determine whether the property (and the corresponding feature) is public or internal, stable or unstable.

Shared scheme

```

import java.util.Collection;
import java.util.HashSet;
import java.util.Objects;
import java.util.Set;
import java.util.regex.Pattern;

/**
 * Represent rules for tests enforced by the @{link {@link TestingConventionsTasks}}
 *
 * Rules are identified by name, tests must have this name as a suffix and implement one of the base classes
 * and be part of all the specified tasks.
 */