Another thing to add to
the agenda which we need to discuss is dependency scopes.
In particular, we need to review our previous decision to
make the implementation component of a module
runtime-scoped, in light of the fact that we now no longer
have combined jars.
Isn't the idea of having an API and implementation split is
that you should not be compiling against anything in the
implementation? Of course, an end user can choose to override
that convention to make the implementation a compile-time
scope, but we don't want to encourage that, do we?
-Dan
--