Re: [jboss-as7-dev] Coping with cyclic test dependencies

I looked into this and it turns out that it cannot get fixed easily. For background info: We used to have the ARQ server side components available as a subsystem. This is the thing that receives the remote JMX invocation, runs JUnit on the server and reports the test results back. It was then decided to remove that subsystem and provide these services dynamically as part of the ARQ TestSuite#Start lifecycle. The code that was contained in the ARQ subsytem is now assembled on the client side and deployed to AS as the arquillian-service deployment. This ARQ deployment has a few dependencies on the server components and the OSGi subsystem. The dependency on OSGi is necessary because test class loading works differently when the test case is contained in a bundle. Additionally the osgi subsystem needs to be bootstrapped if there is a test deployment that needs it. The API incompatibilities could be overcome but there is also a fundamental semantic change with respect to 7.2.1.Final. We now have a Module attached to the DU for a successfully resolved bundle. This however is an error condition in the 7.2.1.Final ARQ service. I propose to release a recent snapshot of the jboss-as/arquillian maven modules. That 3rd party can use to run their tests against the 7.2.x code base. cheers --thomas On 09/17/2012 05:12 PM, Paul Robinson wrote: -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler JBoss OSGi Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx