import org.apache.maven.project.MavenProject;
import org.apache.maven.project.ProjectBuildingException;

/**
 * Strategy to collect projects based on the <code>-f</code> CLI parameter or the pom.xml in the working directory.
 */
@Named("RequestPomCollectionStrategy")
@Singleton
public class RequestPomCollectionStrategy implements ProjectCollectionStrategy {
    private final ProjectsSelector projectsSelector;

    @Inject

    /**
     * Resources to include with the generated documentation.
     */
    public abstract ConfigurableFileCollection getResources();

    /**
     * Location to stage the intermediate documentation. This is like a working directory.
     */
    public abstract DirectoryProperty getStagingRoot();

    public abstract RegularFileProperty getGeneratedMetaDataFile();

    /**

def test_get(client: TestClient):
    response = client.get("/")
    assert response.json() == {"custom_field": [1.0, 2.0, 3.0]}


def test_typeadapter():
    # This test is only to confirm that Pydantic alone is working as expected
    from pydantic import (
        BaseModel,
        ConfigDict,
        PlainSerializer,
        TypeAdapter,
        WithJsonSchema,
    )

    class FakeNumpyArray:

  <groupId>com.example.group</groupId>
  <artifactId>valid-version-sha1plus</artifactId>
  <version>${sha1}${wrong}</version>

  <description>
    This will test if the validation for the ci friendly versions
    is working correct.
  </description>

  <groupId>com.example.group</groupId>
  <artifactId>valid-version-wrong</artifactId>
  <version>${wrong}</version>

  <description>
    This will test if the validation for the ci friendly versions
    is working correct.
  </description>

  <groupId>com.example.group</groupId>
  <artifactId>valid-version-revision</artifactId>
  <version>${revision}</version>

  <description>
    This will test if the validation for the ci friendly versions
    is working correct.
  </description>

    void testCalculationOfBuildPlanWithIndividualTaskWherePluginIsSpecifiedInThePom() throws Exception {
        // We are doing something like "mvn resources:resources" where no version is specified but this
        // project we are working on has the version specified in the POM so the version should come from there.
        File pom = getProject("project-basic");
        MavenSession session = createMavenSession(pom);

  <artifactId>valid-version-sha1</artifactId>
  <version>${revision}${changelist}${sha1}</version>

  <description>
    This will test if the validation for the ci friendly versions
    is working correct.
  </description>

    using an older version of Guava or a build system other than Gradle, they
    may see class conflicts. If so, they can solve them by manually excluding
    the listenablefuture artifact or manually forcing their build systems to
    use 9999.0-....
  </description>
  <build>
    <plugins>
      <plugin>
        <artifactId>maven-source-plugin</artifactId>
      </plugin>
      <plugin>

  </parent>
  <groupId>com.example.group</groupId>
  <artifactId>valid-version-wrong</artifactId>
  <version>1.0</version>

  <description>
    This will test if the validation for the parent version
    is working correct in case of usage of RELEASE
  </description>