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
