I'm wondering about two things: - native libs - integration and unit tests
I am assuming that unit tests will simply use the standard JUnit stuff, so no worries there. But what is your plan for integration testing? It would be _really_ nice to have the build framework set up some kind of runtime environment for this. Another thing I was considering is during runtime, if the "deployment mode" were set to "development", then at Bundle.start(), maybe some kind of diagnostics/tests could be run as part of the cycle. Just a thought. I don't see anything explicit about native libraries in there. I assume you've not forgotten about those? And if the BundleDescriptor produces the pom, what about: - pom hierarchy? - plugins How do you treat those? What's the plan? Cheers, Dave On Feb 6, 2007, at 11:36, Niclas Hedhman 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. > >> Another thing is, [Import Package] needs to be satisfied by some >> exporting bundles. How are we going to wire this? Would there be some >> kind of metadata describing what exporting packages available in each >> ops4j bundle repository for easy lookup? > > Ah! Yes, this is needed. I think this is quite a big change from > the current > dev diagram. The source packages should be first class citizens and > referenced accordingly. > > Now when thinking about it, I think we should also model the > "compile process" > very differently from the 'packaging' process. If we are going to let > standard Sun Java compiler be involved, the non-exported classes > need to > be "stripped" from dependent bundles and question is whether > additional > constraints (versions, uses, attributes, directives) are to be > supported. It > will get hairy if one tries. Otherwise, one need to look for IBM > Equinox/J9 > compiler... > > > Cheers > Niclas > > > _______________________________________________ > general mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/general _______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
