On Fri, 10 Oct 2008 03:00:38 Zoltan Farkas wrote:
> I believe using dependencyManagement actually helps you... it gives you
> the power to control the dependency versions...
in very simple cases it helps and with the import scope it can be quite useful
but its more difficult to understand the result of depedency resolution.

The issue I have is that depedency management is an attempt to force a version
of a library but from outside of the resolution tree. It has side effects and
ultimately it makes it harder to manage dependencies because it makes it easy
consolidate all your version for a short term gain.

For a small project it makes sense and works. For larger projects it does not.
And I take the java view, fewer more well understood approaches to problems
leads to better code sometimes more verbose but easy to understand.

But even more than that when I manage versions of external libraries I just
just manage versions, I also manage related libraries and exclusions and
probably the most important: I provide an independent "release cycle" from
the upstream projects which means all my projects can be exposed in stages to
upstream releases.

I fear that most of the things I say will make no sense to windows and linux
users and a reaonsable portion of linux users who don't really understand how
far package management has come and its parallels with maven.

>
> from the doc:
>
> "very important use of the dependency management section is to control
> the versions of artifacts used in transitive dependencies"
>
> --zoly


--
Michael McCallum
Enterprise Engineer
mailto:gholam@(protected)

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@(protected)
For additional commands, e-mail: users-help@(protected)