yes, people can still make mistakes, but at least when they are fixed its easy to see all places affected.
even currently it offers a lot of advantages. for example when working on request module you cannot mistaking add a dependency on Application or Component or somethign else core-specific because it is not in that module. if someone would move Application or Component mistakingly into that module i think it would be easily noticed. -igor On Tue, Jan 25, 2011 at 11:36 AM, James Carman <ja...@carmanconsulting.com> wrote: > On Tue, Jan 25, 2011 at 11:50 AM, Jeremy Thomerson > <jer...@wickettraining.com> wrote: >> >> The separate modules is a good way to enforce the separation. If you have >> other ideas for enforcing them, I'd be happy to hear them. >> > > It doesn't really enforce anything. Folks can still put classes in > the wrong module and screw things up. So, either way, you're adhering > to a convention. So, why muddy up the project structure? >
