On Aug 16, 2011, at 20:48, Dan Allen <[email protected]> wrote: > On Tue, Aug 16, 2011 at 22:27, Shane Bryzak <[email protected]> wrote: > 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
I'm with Dan on this one. That's the whole point of impl and api. > -- > Dan Allen > Principal Software Engineer, Red Hat | Author of Seam in Action > Registered Linux User #231597 > > http://www.google.com/profiles/dan.j.allen#about > http://mojavelinux.com > http://mojavelinux.com/seaminaction >
_______________________________________________ seam-dev mailing list [email protected] https://lists.jboss.org/mailman/listinfo/seam-dev
