Bug 724650 (BRMS-555)

Summary:	Provide Drools tests JARs as part of the build output and publish those test from productization to QE
Product:	[JBoss] JBoss Enterprise BRMS Platform 5	Reporter:	Lukáš Petrovický <lpetrovi>
Component:	Build Process	Assignee:	trev <tkirby>
Status:	VERIFIED ---	QA Contact:	Lukáš Petrovický <lpetrovi>
Severity:	low	Docs Contact:
Priority:	high
Version:	unspecified	CC:	atangrin, ge0ffrey.spam, lpetrovi
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/BRMS-555
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Task
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Lukáš Petrovický 2011-02-21 13:39:34 UTC

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.

Comment 1 Geoffrey D Smet 2011-02-21 19:26:33 UTC

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?

Comment 2 Lukáš Petrovický 2011-02-22 08:37:25 UTC

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.

Comment 3 Geoffrey D Smet 2011-02-22 09:45:29 UTC

Thanks for the clarification. I 've adjusted the title to make this clear and assigned it to Trevor.

Comment 4 Lukáš Petrovický 2011-04-26 12:09:57 UTC

Link: Added: This issue is a dependency of JBQA-4464

Comment 5 Lukáš Petrovický 2011-08-01 06:48:22 UTC

Changing priority to low as we've already worked around the issue in our test suite.

Comment 6 Lukáš Petrovický 2011-09-16 14:12:47 UTC

And now we even have access to the productization's Maven repo. I'm marking this as VERIFIED.