It’s also an attempt to create a modular system, in hopes of minimizing codebase size and providing custom functionality. It’s thus closely related to a lot of the modularity ideas that have come and gone over time, without the judgment of what is properly a “module.” I’ve seen multi-hundred module projects.
On Nov 22, 2013, at 1:33 PM, Ron Wheeler <rwhee...@artifact-software.com> wrote: > Looks like a kludge to get around a poor SOA architecture with too many > inter-module dependencies and an unwillingness to build mock objects for > testing. > > In our house, SNAPSHOTS posted to Nexus come with a warranty that they meet a > subset of the spec that is known. > If someone doesn't like that level of instability, they should make mock > objects that they understand. > > Ron > > > On 22/11/2013 11:11 AM, Viktor Sadovnikov wrote: >> Hello, >> >> Here is an interesting article about dependencies management and builds >> with Maven, which can become unnecessary overcomplicated >> http://bit.ly/1dn9ZZL >> >> With regards, >> Viktor >> > > > -- > Ron Wheeler > President > Artifact Software Inc > email: rwhee...@artifact-software.com > skype: ronaldmwheeler > phone: 866-970-2435, ext 102 > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > ----------------- Author, Getting Started with Apache Maven <http://www.packtpub.com/getting-started-with-apache-maven/video> Come read my webnovel, Take a Lemon <http://www.takealemon.com>, and listen to the Misfile radio play <http://www.fuzzyfacetheater.com/misfile/>!
