There are a couple of maven targets for this:
maven bootstrap:run maven bootstrap:debug
These targets do not rely on any files being copied anywhere: they run entirely using jars in the local maven repository and a couple of configuration files in the source tree. The classpath should be fairly easily computable based on the project dependencies, but I leave this task for later or for others.
Several of the new classes in the deployment module may have a short lifetime: they generally imitate the current xml processing and provide a convenient way to construct a configuration without a lot of infrastructure.
The current deployment runs on the server that constructs the Configuration, I haven't tried to distribute it yet.
The way it works is:
You supply a gbean configuration file on the command line to Bootstrap. Bootstrap constructs a BatchDeployer including only a ServiceDeployer, and loads and starts this configuration.
The configuration, in turn, has a BatchDeployerFactory GBean that collects other deployers deployed as gbeans in a "Deployers" endpoint. In particular, there is a web deployer. There are also the other gbeans needed to run the web server.
Finally, there is an ExplicitDeployment gbean that holds the package you wish to deploy (web-console, in this case). It gets a new BatchDeployer from the BatchDeployerFactory, with all deployed deployers, and tries to deploy the package. In this way you don't need a deployment scanner.
David Jencks
