>
> Michal, does your change take imports nesting into account?
>
Yes, my patch determines distance between dependencies based on depth of a
particular dependency - and nesting is supported. However I'm still working
on an approach that will not change generated maven model classes as this
is more
Hi,
I did some research not so long ago to find out the way managed dependency
versions are resolved and ended up with a following logical lookup
algorithm:
Whichever is encountered first:
1. for each pom up the hierarchy:
a. concrete dependency
b. managed dependency
2. for each pom up the h
Am 2016-01-02 um 17:00 schrieb Michał Kowalcze:
Basically it's in https://issues.apache.org/jira/browse/MNG-5947 along with
example POMs. Graphically - having imports in dependency management like:
final:1.0
+ import:1.0
+ parent:3.2.1
+ commons-collections:3.2.1
Basically it's in https://issues.apache.org/jira/browse/MNG-5947 along with
example POMs. Graphically - having imports in dependency management like:
final:1.0
+ import:1.0
+ parent:3.2.1
+ commons-collections:3.2.1
+ parent:3.2.2
+ commons-collections:3.
Perhaps it might help to describe what you did, what you expected to
happen and what actually happened.
Ron
On 02/01/2016 10:28 AM, Michał Kowalcze wrote:
Hello!
I've played a bit with maven dependency management section and basically
pom import in dependency management section does not suppo
Hello!
I've played a bit with maven dependency management section and basically
pom import in dependency management section does not support at all
"nearest-wins" strategy for resolving conflicts. The only one supported
option is first match.
I did not found anything in documentation about this be
