As I have spoken with Shane in IRC, why not merge Solder API and Impl into one module only ? I mean, is there a strong reason for them to exist ? It will make it easier for end users (and seam modules also)
2011/8/17 Dan Allen <[email protected]>: > On Tue, Aug 16, 2011 at 23:05, Dan Allen <[email protected]> wrote: >> >> On Tue, Aug 16, 2011 at 22:57, Shane Bryzak <[email protected]> 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. > -Dan > -- > 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 > > _______________________________________________ seam-dev mailing list [email protected] https://lists.jboss.org/mailman/listinfo/seam-dev
