<url>https://javadoc.io/doc/com.google.j2objc/j2objc-annotations/latest/</url>
              <location>${project.basedir}/javadoc-link/j2objc-annotations</location>
            </offlineLink>
            <offlineLink>
              <url>https://errorprone.info/api/latest/</url>
              <location>${project.basedir}/javadoc-link/error_prone_annotations</location>
            </offlineLink>
          </offlineLinks>

    @Override
    public void apply(Project project) {
        project.getRootProject().getPluginManager().apply(DockerSupportPlugin.class);
        project.getPlugins().apply(InternalDistributionDownloadPlugin.class);
        project.getPlugins().apply(JdkDownloadPlugin.class);
        project.getPluginManager().apply("elasticsearch.build");

    // reason it isn't ? This localization is kind-of a code smell.

    public static String getKey(MavenProject project) {
        return project.getGroupId() + ':' + project.getArtifactId() + ':' + project.getVersion();
    }

            // This test mainly verifies that apply goal can modify files
        }
    }

    @Nested
    @DisplayName("Multi-module Projects")
    class MultiModuleTests {

        @Test
        @DisplayName("should handle multi-module project structure")
        void shouldHandleMultiModuleProject() throws Exception {
            // Create parent POM
            Path parentPom = tempDir.resolve("pom.xml");

package projects

import common.FlakyTestStrategy
import common.HIDDEN_ARTIFACT_DESTINATION
import common.Os
import common.uuidPrefix
import configurations.BaseGradleBuildType
import configurations.DocsTestProject
import configurations.DocsTestTrigger
import configurations.FlakyTestQuarantineProject
import configurations.FlakyTestQuarantineTrigger
import configurations.FunctionalTest
import configurations.FunctionalTestsPass

platforms/core-configuration/declarative-dsl-core/                  @gradle/bt-declarative-gradle-project
platforms/core-configuration/declarative-dsl-evaluator/             @gradle/bt-declarative-gradle-project
platforms/core-configuration/declarative-dsl-provider/              @gradle/bt-declarative-gradle-project

              <compileSourceRoots>
                <compileSourceRoot>${project.basedir}/src</compileSourceRoot>
              </compileSourceRoots>

              <!-- JPMS needs access to the module sources to complete a modular Java build. -->
              <compilerArgs>
                <arg>-sourcepath</arg>
                <arg>${project.basedir}/src</arg>
                <arg>--add-reads=com.google.common=ALL-UNNAMED</arg>

            associated with a Maven project can lack a file. As such, this annotation is meant for Mojos that only
            want to analyze the set of transitive dependencies, in particular during early lifecycle phases where
            full dependency resolution might fail due to projects which haven't been built yet.
          </description>
        </field>
        <field>

Eu nunca fui capaz de usá-lo em um projeto completo, pois ele não tinha integração de segurança, então, eu não pude substituir todos os recursos que eu tinha com os geradores full-stack baseados no Flask-apispec. Eu tinha no meu backlog de projetos criar um pull request adicionando essa funcionalidade.

Mas então, o foco do projeto mudou.

Use `Objects.requireNonNull` statement or `Preconditions` rather than `assert` or `@SuppressWarning` annotation to suppress if possible.

For gradual adoption, enable checks project-by-project.
Do not rely on `@NullMarked` annotations.
Only enable checks for a project if all its dependencies have checks enabled, in order to avoid back-and-forth when refining the annotations.