On 15 March 2010 22:29, Ron Wheeler <rwhee...@artifact-software.com> wrote:
> Am I missing something?
>
> There seem to be a lot of people who try to incorporate jar projects into
> master projects and deploy with the "Big Bang" Theory - Get everything "all
> right" and deploy the whole mess.
>
> They seem to generate a lot of problems for themselves.
>
> Is it not a better idea to build projects for your libraries separately,
> test them, deploy them on their own and then use them as dependencies in the
> same way that one uses dependencies from third parties?
Hi Ron,
This sounds like it might be slightly influenced by my thread from
yesterday, or at least is related to it.
You are generally right about the best practice - modular development
is almost always a good idea, but I doubt you would find a way to
significantly cut down on the traffic here, as there are definitely a
lot of special cases, as I know only too well.
Also, managing lots of completely independent pieces of code is hard
work. Even Maven itself is several modules combined into a project,
so that a single command can build/deploy lots of pieces at once.
When synchronizing releases across modules, this is really an obvious
win.
There are some definite patterns that Maven makes work well, and maybe
collecting these together would be help to people. For example, the
pattern of project/{core,web-app,cli-app}, or
project/{ejbs,utils,web-app,ear-app}.
And indeed considering these patterns can help with abstracting out
some other cases, but there will always be some things that will be
more complicated. My case involves something like one of the above
patterns, but with custom deployment requirements, and several new
packaging types, it can't be made to map neatly into a simple "build
the parts, then assemble" pattern - so I came here and asked for help.
<snip>
>
> Ron
>
--
Phil Housley
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
