Description

<dependency>
    <groupId>io.github.slavytuch</groupId>
    <artifactId>doqa-junit5</artifactId>
    <version>0.2.1</version>
</dependency>

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
    <modelVersion>4.0.0</modelVersion>

    <parent>
        <groupId>io.github.slavytuch</groupId>
        <artifactId>doqa-java</artifactId>
        <version>0.2.1</version>
    </parent>

    <artifactId>doqa-junit5</artifactId>
    <packaging>jar</packaging>

    <name>DoQA JUnit 5 adapter</name>
    <description>
        JUnit 5 adapter for DoQA: reports test results with steps, fixtures, parameters,
        attachments and links either directly to the DoQA API or as Allure-compatible result
        files, driven by annotations (@DoqaId, @DoqaTitle, ...), the Doqa runtime API
        and AspectJ @Step weaving.
    </description>

    <dependencies>
        <!-- framework-agnostic core: Doqa facade, annotations, @Step aspect, attribution,
             result projection and the reporting session (brings doqa-client transitively). -->
        <dependency>
            <groupId>io.github.slavytuch</groupId>
            <artifactId>doqa-java-commons</artifactId>
            <version>${project.version}</version>
        </dependency>

        <!-- provided: the host test project already has the JUnit Platform on the classpath. -->
        <dependency>
            <groupId>org.junit.platform</groupId>
            <artifactId>junit-platform-launcher</artifactId>
            <version>${junit.platform.version}</version>
            <scope>provided</scope>
        </dependency>
        <dependency>
            <groupId>org.junit.platform</groupId>
            <artifactId>junit-platform-engine</artifactId>
            <version>${junit.platform.version}</version>
            <scope>provided</scope>
        </dependency>
        <dependency>
            <groupId>org.junit.jupiter</groupId>
            <artifactId>junit-jupiter-api</artifactId>
            <version>${junit.jupiter.version}</version>
            <scope>provided</scope>
        </dependency>

        <!-- The @Step aspect (aspectjrt) arrives via doqa-java-commons; the weaver is the
             host's responsibility (LTW via -javaagent or the aspectj-maven-plugin at build time). -->
        <dependency>
            <groupId>org.aspectj</groupId>
            <artifactId>aspectjweaver</artifactId>
            <version>${aspectj.version}</version>
            <scope>provided</scope>
        </dependency>

        <dependency>
            <groupId>org.junit.jupiter</groupId>
            <artifactId>junit-jupiter</artifactId>
            <version>${junit.jupiter.version}</version>
            <scope>test</scope>
        </dependency>
    </dependencies>

    <build>
        <plugins>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-compiler-plugin</artifactId>
                <configuration>
                    <!-- real argument names for @ParameterizedTest parameters / {param}
                         placeholders (hosts should enable the same, else names are arg0..argN). -->
                    <parameters>true</parameters>
                </configuration>
            </plugin>
            <!-- Exposes ${org.aspectj:aspectjweaver:jar} for the surefire javaagent below. -->
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-dependency-plugin</artifactId>
                <executions>
                    <execution>
                        <phase>initialize</phase>
                        <goals>
                            <goal>properties</goal>
                        </goals>
                    </execution>
                </executions>
            </plugin>
            <!-- LTW agent so the E2E launcher test exercises the @Step aspect exactly like a host
                 build (see README: hosts add the same -javaagent to their surefire/gradle test JVM). -->
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-surefire-plugin</artifactId>
                <configuration>
                    <!-- add-opens: on JDK 16+ the weaver must define generated around-advice
                         closure classes (\$AjcClosure) reflectively; hosts need the same flag. -->
                    <argLine>-javaagent:${org.aspectj:aspectjweaver:jar} --add-opens java.base/java.lang=ALL-UNNAMED</argLine>
                    <systemPropertyVariables>
                        <!-- The outer test run never reports anywhere, whatever DOQA_* the
                             machine exports; nested launches opt in per test. -->
                        <doqa.reporting>off</doqa.reporting>
                        <!-- Any stray file-sink output lands under target/, not the repo root. -->
                        <doqa.resultsDir>${project.build.directory}/results</doqa.resultsDir>
                    </systemPropertyVariables>
                </configuration>
            </plugin>
        </plugins>
    </build>
</project>