Ok here's a special case - how about the Mutable
interface/AbstractMutable? These classes are used in the drools,
framework, spring and persistence modules, and are referenced in the
JavaBeanInterceptor and RootInterceptor.
Pete Muir wrote:
On 22 Apr 2009, at 20:56, Dan Allen wrote:
> On Wed, Apr 22, 2009 at 4:18 AM, Shane Bryzak
> <shane.bryzak(a)jboss.com> wrote:
> These two were just examples, in reality there's a lot more than
> that. I do like the idea though of making the modules as independent
> as possible, so for now I'll just copy any utility classes that are
> required into the module itself.
>
> If it's a whole file (meaning not just a copied method), it should be
> easy enough to reference the source and then we can be sure they are
> kept in sync. Obviously, that doesn't scale infinitely, but I believe
> Pete is saying that we want to see how it goes before deciding to
> replant ;)
Right, no point in copying methods you won't use into a module, just
because they exist.
This is a really a 50:50 situation - both copying and dependencies
have bad points...
>
>
> -Dan
>
> --
> Dan Allen
> Senior Software Engineer, Red Hat | Author of Seam in Action
>
>
http://mojavelinux.com
>
http://mojavelinux.com/seaminaction
>
http://in.relation.to/Bloggers/Dan
>
> NOTE: While I make a strong effort to keep up with my email on a daily
> basis, personal or other work matters can sometimes keep me away
> from my email. If you contact me, but don't hear back for more than a
> week,
> it is very likely that I am excessively backlogged or the message was
> caught in the spam filters. Please don't hesitate to resend a
> message if
> you feel that it did not reach my attention.
--
Pete Muir
http://www.seamframework.org
http://in.relation.to/Bloggers/Pete