final BoolQueryBuilder boolQuery = QueryBuilders.boolQuery();
        for (final BooleanClause clause : booleanQuery.clauses()) {
            final QueryBuilder queryBuilder = getQueryProcessor().execute(context, clause.query(), boost);
            if (queryBuilder != null) {
                switch (clause.occur()) {
                case MUST:
                    boolQuery.must(queryBuilder);
                    break;

        }

    fun getDependencies() = classes.map { it.value.outputClassFilename to it.value.dependencies.map { it.outputClassFilename } }.toMap()
}


class ClassDetails(val outputClassName: String) {
    var visited: Boolean = false
    val dependencies: MutableSet<ClassDetails> = linkedSetOf()
    val outputClassFilename
        get() = "$outputClassName.class"
}


class PackagePatterns(givenPrefixes: Set<String>) {

     */
    byte FS_SIZE_INFO = 3;
    /**
     * File system full size information constant.
     */
    byte FS_FULL_SIZE_INFO = 7;

    /**
     * Gets the file system information class.
     *
     * @return file system information class
     */
    byte getFileSystemInformationClass();

 * subclasses. Without such overrides, optimizers might put a {@code writeReplace}-containing class
 * and its subclass in different packages, causing the serialization system to fail to invoke {@code
 * writeReplace} when serializing an instance of the subclass. For an example of this problem, see
 * b/310253115.
 */
@NullUnmarked
public class WriteReplaceOverridesTest extends TestCase {
  private static final ImmutableSet<String> GUAVA_PACKAGES =

/** Exception classes for use in tests. */
@GwtCompatible
final class TestExceptions {
  static final class SomeError extends Error {}

  static final class SomeCheckedException extends Exception {}

  static final class SomeOtherCheckedException extends Exception {}

  static final class YetAnotherCheckedException extends Exception {}

  static final class SomeUncheckedException extends RuntimeException {}

            // Verify method is inherited
            assertNotNull(AllocInfo.class.getMethod("decode", byte[].class, int.class, int.class));
            assertEquals(int.class, AllocInfo.class.getMethod("decode", byte[].class, int.class, int.class).getReturnType());
        }

        @Test
        @DisplayName("Should have FileSystemInformation constants accessible")
        void shouldHaveFileSystemInformationConstants() {

## Benutzerdefinierte Response-Klasse { #custom-response-class }

Sie können Ihre eigene benutzerdefinierte Response-Klasse erstellen, die von `Response` erbt und diese verwendet.

Actually, `Query`, `Path` and others you'll see next create objects of subclasses of a common `Param` class, which is itself a subclass of Pydantic's `FieldInfo` class.

And Pydantic's `Field` returns an instance of `FieldInfo` as well.

`Body` also returns objects of a subclass of `FieldInfo` directly. And there are others you will see later that are subclasses of the `Body` class.

          <association xml.itemsStyle="flat">
            <type>CoreExtension</type>
            <multiplicity>*</multiplicity>
          </association>
        </field>
      </fields>
    </class>
    <class xml.tagName="extension">
      <name>CoreExtension</name>
      <description>Describes a build extension to utilise.</description>
      <version>1.0.0+</version>
      <fields>
        <field>

 * TODO: this is session scoped as SPI can contribute.
 */
@Named
@Singleton
public class DefaultLifecycleRegistry implements LifecycleRegistry {

    private static final String MAVEN_PLUGINS = "org.apache.maven.plugins:";

    public static final String DEFAULT_LIFECYCLE_MODELID = "org.apache.maven:maven-core:"
            + DefaultLifecycleRegistry.class.getPackage().getImplementationVersion()
            + ":default-lifecycle-bindings";