Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Userguide is inconsistent with jboss-tck-runner examples in CDI TCK dist #378

Closed
starksm64 opened this issue Jun 3, 2022 · 1 comment
Closed

Comments

@starksm64
Copy link
Contributor

The userguide shows the following setup for the Web Profile:

      <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-surefire-plugin</artifactId>
            <configuration>
                <excludedGroups>javaee-full</excludedGroups>
            </configuration>
       </plugin>

and no example setup for the Full Platform. However, the jboss-tck-runner/pom.xml setup uses the following for the Web Profile:

      <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-surefire-plugin</artifactId>
            <configuration>
                <excludedGroups>javaee-full,se</excludedGroups>
            </configuration>
       </plugin>

and the following for the Full Platform:

      <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-surefire-plugin</artifactId>
            <configuration>
                <excludedGroups>se</excludedGroups>
            </configuration>
       </plugin>

It really makes no sense to require a Jakarta EE server to support the Java SE CD APIs as it is a completely separate launch mode that would require a separate Arquillian container configuration. The userguide needs to be consistent with the WildFly/Weld jboss-tck-runner example.

@starksm64
Copy link
Contributor Author

This was updated in the 4.0.3 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant