Craig Ching <[EMAIL PROTECTED]> writes: > Has anyone done this or anything like this?
Yes, but we've only "solved" it by not solving it and faking it. Maven's "provided" scope doesn't quite apply for bundles, as the entire bundle's class space should not be on the consumer's class path at compile-time. Similarly, "runtime" scope isn't appropriate either. The (entire) bundle should not be available on the compile-time class path, nor should it be available at run-time unmitigated by an intervening OSGi framework. In cases where we do need compile-time dependency on portions of a bundle, we specify it at "provided" scope and force the developer to be diligent about not relying on non-exported packages in the bundle. Unfortunately, these transgressions will only show up as package resolution errors in the OSGi framework when the bundle under development attempts resolution. -- Steven E. Harris --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
