<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

## Code includes with unknown attributes { #code-includes-with-unknown-attributes }

{* ../../docs_src/python_types/tutorial001_py310.py unknown[123] *}

## Some more code includes to test fixing { #some-more-code-includes-to-test-fixing }

{* ../../docs_src/dependencies/tutorial013_an_py310.py ln[19:21] *}

{* ../../docs_src/bigger_applications/app_an_py310/internal/admin.py hl[3] title["app/internal/admin.py"] *}

<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

<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

     */
    @Nonnull
    Optional<Boolean> infer();

    /**
     * Should fix Maven 4 compatibility issues in POMs.
     * This includes fixing unsupported combine attributes, duplicate dependencies,
     * unsupported expressions, and other Maven 4 validation issues.
     *
     * @return an {@link Optional} containing the boolean value {@code true} if specified, or empty

import org.apache.maven.execution.ExecutionEvent;
import org.apache.maven.execution.ExecutionListener;
import org.apache.maven.execution.MavenSession;
import org.apache.maven.plugin.MojoExecution;

/**
 * Assists in firing execution events. <strong>Warning:</strong> This is an internal utility class that is only public
 * for technical reasons, it is not part of the public API. In particular, this class can be changed or deleted without
 * prior notice.

<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

5. On the date that the fixes are applied a security advisory will be published on <https://blog.min.io>.
   Please inform us in your report email whether MinIO should mention your contribution w.r.t. fixing
   the security issue. By default MinIO will **not** publish this information to protect your privacy.

This process can take some time, especially when coordination is required with maintainers of other projects.

            dependencies.add(sourceSet.getRuntimeElementsConfigurationName(), projectDependency);
        });
        // PolicyUtil doesn't handle classifier notation well probably.
        // Instead of fixing PoliceUtil we stick to the pattern of changing
        // the basename here to indicate its a test artifacts jar.
        BasePluginExtension pluginExtension = project.getExtensions().getByType(BasePluginExtension.class);

name: Bug Report
description: Something is not working as expected
labels: ["type=defect"]
body:
  - type: markdown
    attributes:
      value: >
        Thank you for filing a bug report. Please help us identify and resolve the bug by filling
        out the following fields. Before we begin, please make sure that the bug is still present in
        the [latest](https://github.com/google/guava/releases/latest) version of Guava available.