-
Task
-
Resolution: Done
-
Major
-
None
-
None
In the root pom we define these properties:
<!-- Galleon feature pack to use in testsuite provisioning executions that provide content
that *cannot* be obtained solely from the wildfly-ee-galleon-pack or its dependencies.
Test jobs can override this using -D to test using a different feature pack.
-->
<testsuite.full.galleon.pack.groupId>${full.maven.groupId}</testsuite.full.galleon.pack.groupId>
<testsuite.full.galleon.pack.artifactId>wildfly-galleon-pack</testsuite.full.galleon.pack.artifactId>
<testsuite.full.galleon.pack.version>${full.maven.version}</testsuite.full.galleon.pack.version>
But in testsuite/integration/microprofile-tck we define different ones:
<!-- Child modules override these properties to control what feature packs are used
and what layers are provisioned if galleon provision occurs -->
<ts.microprofile-tck-provisioning.fp.groupId>${full.maven.groupId}</ts.microprofile-tck-provisioning.fp.groupId>
<ts.microprofile-tck-provisioning.fp.artifactId>wildfly-galleon-pack</ts.microprofile-tck-provisioning.fp.artifactId>
<ts.microprofile-tck-provisioning.fp.version>${full.maven.version}</ts.microprofile-tck-provisioning.fp.version>
The mp-tck modules should use the properties from the root pom.
