On 25/06/07, Kenney Westerhof <[EMAIL PROTECTED]> wrote:
Mark Hobson wrote:
> Now, there are three solutions: 1) Update all other components that
> also depend on this dependency so there are no version conflicts; 2)
> Add the bug fix version to the main project's depMan; 3) Rely on the
> conflict resolution strategy to resolve the required version.
>
> (1) becomes extremely impractical in large projects; (2) works, but
> over time, as more and more versions are fixed in depMan, it starts to
> resemble Maven 1's flattened list of dependencies, thus causing even
> more maintenance problems; (3) seems like the most natural place to
> make these decisions.
2 doesn't work without stripping all version tags on that dependency from
all modules, as depMan only provides defaults for direct deps.
Not sure if I understand you here - my understanding is:
- depMan overrides versions for transitive dependencies
- direct dependencies override versions from depMan
3 doesn't always work - if you build a sub-tree of modules that doesn't
have any dep with the bugfix version you still get the older one, so, what
version you'll get will depend on where you build (how big the reactor is).
True, but I think this is preferable to a project's dependencies'
versions changing depending on their depth.
Cheers,
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
