On Aug 16, 2011, at 21:06, Dan Allen <dan.j.allen(a)gmail.com> wrote:
On Tue, Aug 16, 2011 at 23:05, Dan Allen
On Tue, Aug 16, 2011 at 22:57, Shane Bryzak <sbryzak(a)redhat.com> wrote:
Of course, but we break that rule. Solder is one example, there's multiple utility
classes in the implementation that are required to compile other modules.
I consider that a bug (or a work in progress, depending on how you look at it).
An API is an API. If it's an "internal API", then perhaps it should be an
SPI. Under no circumstances should we be depending on implementation classes between
modules. Otherwise, we are changing the definition of an implementation.
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597