Hide Forgot
securitylevel_name: Public Currently QE build their own Drools test JARs, which creates all sorts of problems. If we could get the test JARs alongside a build, that would be excellent. However, since we're sharing the testing tools, this would need to happen for SOA as well. Generally it should both happen via setting the same Maven flag.
The drools parent pom has been building the test-jar for a couple of months already: https://github.com/droolsjbpm/droolsjbpm-build-bootstrap/blob/master/pom.xml#L377 <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-jar-plugin</artifactId> <version>2.3.1</version> <executions> <execution> <goals> <goal>test-jar</goal> </goals> </execution> </executions> The test-jars should also be deployed to nexus. More info at http://maven.apache.org/guides/mini/guide-attached-tests.html So I don't understand the problem. One possible corner case: I don't know how that configuration affects war packaging, such as guvnor-webapp (formerly known as drools-guvnor). Of what artifact are you missing the test jars?
We are aware that the Drools parent Pom is set up for building the tests. However, the productization team is not publishing the tests to us - so this is what this task is about.
Thanks for the clarification. I 've adjusted the title to make this clear and assigned it to Trevor.
Link: Added: This issue is a dependency of JBQA-4464
Changing priority to low as we've already worked around the issue in our test suite.
And now we even have access to the productization's Maven repo. I'm marking this as VERIFIED.