Niclas Hedhman wrote: > On Mon, Jun 16, 2008 at 5:36 PM, Rickard Öberg <[EMAIL PROTECTED]> wrote: >> Niclas Hedhman wrote: >>> You will of course need the runtime.jar at deployment time, but for >>> dependency declarations, I would like to have a reflective lookup >>> (like the JRE's service/extension mechanisms) of both runtime and spi >>> providers in bootstrap, so "most code" only declare dep on >>> api+bootstrap (or maybe even move bootstrap classes into API). >> As it is bootstrap only exposes API classes, so to use it there's no >> need to add depedency on runtime. Isn't that enough? What is not >> accomplished by that? > > I don't think I understand your statement. > > Right now, bootstrap depends on runtime. This creates a transitive > dependency in "my code" on the qi4j-core-runtime.jar, and "my code" > has the Runtime classes visible, and that can/will be abused.
Even though the bootstrap only exposes API classes, and the dependency is internal? I thought you only got the dependency on bootstrap. /Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
