JavaTestDeploymentPackager should resolve the protocol.jar from the runner pom.xml using the shrinkwrap resolver

[starksm64]

Currently one needs to have a configuration of the maven-dependency-plugin in your test runner pom.xml to make the javatest protocol server side classes available for inclusion in the deployment artifacts:

            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-dependency-plugin</artifactId>
                <version>3.6.1</version>
                <executions>
                    <execution>
                        <id>copy-protocol-lib</id>
                        <phase>process-test-resources</phase>
                        <goals>
                            <goal>copy</goal>
                        </goals>
                        <configuration>
                            <artifactItems>
                                <artifactItem>
                                    <groupId>jakarta.tck.arquillian</groupId>
                                    <artifactId>arquillian-protocol-lib</artifactId>
                                    <version>${version.jakarta.tck.arquillian}</version>
                                    <type>jar</type>
                                    <overWrite>true</overWrite>
                                    <outputDirectory>${project.build.directory}/protocol</outputDirectory>
                                    <destFileName>protocol.jar</destFileName>
                                </artifactItem>
                            </artifactItems>
                        </configuration>
                    </execution>
                </executions>
            </plugin>

The JavaTestDeploymentPackager should try to resolve the jar file from the test runner pom.xml using the shrinkwrap maven dependency resolver in the next tck tools release.