On Tuesday 06 February 2007 11:33, Stuart wrote: > On 06/02/07, Niclas Hedhman <[EMAIL PROTECTED]> wrote: > > On Tuesday 06 February 2007 10:14, Edward Yakop wrote: > > > > Very good points. > > > > > It seems both the diagram does not address test dependencies. I would > > > assume from dev-model that the test dependencies are defined in > > > [Bundle Descriptor]? > > > > Test is IMHO not a build time concern, and should be modelled separately > > more like a Runtime Configuration (which is how IDEA actually treats it). > > Will try to create some more diagrams with this. > > We should support various integration tests inside an OSGi container - > we can use the runconf-model to define the test setup, but will also > need to define "scenarios", such as a sequence of injected events (ie. > bundle events, service events, client events...) over the lifetime of > the test.
Yes. If we want to be a notch better, it should be possible to set up tests where bundles comes and goes over long-running tests. But this is a massive topic in its own right. > Btw, should the runconf-model show how configurations will be pushed > to the bundles, or is this process specific to each bundle? Are there > any configuration details that we could capture at development time to > help during deployment? I think the runconf-model is about "assembly". Everyone talks about "deployment people" being different from "developers", but I have never seen any evidence of that in real life. So, I will continue with the view (even if it is wrong) that deployment run configurations are defined by developers, but are not strongly tied to any bundle. The Run Conf needs the "Start Descriptors" to maintain sequence, i.e. a List and not a Collection. The mechanism for it to arrive on the platform is probably best left to pax-runner or other deployment tools. > Also, can we split the code into a generic framework that can get > wrapped up as IDEA / Eclipse / NetBeans plugins? Yes, that is the basic idea. Cheers Niclas _______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
