As Karl mentions, DeploymentAdmin is a specification that has answers to some of your questions. You can specify so called deployment packages, which group bundles (and even other artifacts you want to deploy). These packages will be installed and updated in transactions (rolling them back if something fails), and you can even distribute "diffs" from version A to B (so called fix packages). The specification is in the R4.1 compendium and well worth reading.
Furthermore, you mention bundles being started in random order as being "annoying" to developers, stating you want to create a dependency tree of bundles. I think that might be the wrong approach to the problem. Bundles should be able to start in random orders. Any dependencies between bundles should actually be dependencies between services and those can be handled automatically (declarative services, iPOJO, dependency manager, ...). In general, with the flexibility that small bundles give you, comes the complexity of actually managing all those bundles, partitioning them into (many) different configurations and getting those onto targets. Greetings, Marcel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
