Following a call with Kabir, Aslak, David, and myself we agreed
#1 Kabir gets the embedded AS7 to work in JBossASEmbeddedContainer. This is merges his work and my work and generally provides an API that allows AS7 embedded bootstrap with a minimal set of packages (i.e. idealy only org.jboss.modules) on the app classpath
#2 David extends the ARQ JMX protocol to support the notion of events between test case and test client. The use case is that at runtime a test case can fetch additional archives from the test client. Aslak has done some design work around this. Later we port the JMX extension to the new ARQ Event API [JBOSGI-418]
#3 Kabir ports the AS7 demos to ARQ when #1 is done. This should allow the demos to run at build time
#4 I unify the code paths for deployed/installed bundles. Currently, 3rd party OSGi provisioners like the EOSGi JMX API shortcut the DeploymentChain. Generally, BundleContext.installBundle(...) must go through the DeploymentUnitProcessors like for any other deployment. This would allow to get rid of arquillian-osgi-bundle in AS7. The ARQ subsystem would see all deployments. [JBOSGI-427]
#5 Unrelated to ARQ, but here for the record. I provide a ConfigAdmin subsytem that that can be used to maintain the configuration aspects of arbitrary deployments. It would also be compatible with the standard OSGi ConfigAdmin such that 3rd party bundles can get their configuration data from it. The data is maintained as part of the domain model and as such visible/editable by the AS7 management agent. [JBOSGI-425]