Pulling in components for jbossas testsuite runs

[starksm64]

Tom brought up an issue today with jbossws wanting to run tests against the bpel interface of jbpm. Instead of bundling this into the jbossas all build, I'm thinking that this needs to have a target in the testsuite build that combines a testsuite/src/resources/test-configs/ configuration with the jbpm repository binaries.

This brings up an issue with how the server docs/licenses content is created. The jbpm binaries and dependencies should not be showing up in this set of components. Rather, the testsuite itself would need a supplemental thirdparty set of components.

[ryan.campbell]

So we need a build-thirdparty.xml in the testsuite module? Or could we add a tag to the component element which would exclude it (and its dependencies) from the license generation process.

I guess this is a hack, but it is a short-lived one.

[tom.baeyens]

What is the conclusion from this ?

Where should i get started to integrate jbpm in the test suite ?

regards, tom.

[starksm64]

The testsuite build.xml needs to be updated to pull test only binaries from the repository for use in custom jbossas configurations.

[ryan.campbell]

Ok, so here is what we need to do:

1. Create a testsuite/build-thirdparty.xml
2. Add bpel to repository
3. Add bpel to testsuite/build-thirdparty.xml
4. Create a new server-config in testsuite/imports/server-config.xml which pulls in the bpel/jbpm binaries
5. Add a test + test artifacts to src/main
6. Create a target in build/build.xml

I'll create the JIRA task.

[ryan.campbell]

I created the build-thirdparty task and linked it to the existing BPEL task:

http://jira.jboss.com/jira/browse/JBPM-541

Rajesh will make sure the above steps are documented in the testsuite guide clearly enough for Alex to follow.

http://wiki.jboss.org/wiki/Wiki.jsp?page=TestsuiteGuide