On Wed, Sep 14, 2016 at 1:32 PM, Christian Schulte <[email protected]> wrote:

> Am 09/14/16 um 08:42 schrieb Stephane Nicoll:
> > First of all, I'd like the error message to change. I still don't know to
> > this day what it means. Second, if Maven is able to find out that two
> boms
> > provide dependency management for foo with conflicting versions, It would
> > be nice to say in which boms the inconsistency was found.
>
> Can you post such an error message, please. That information should be
> part of it already.
>

I did already in my original email, see https://gist.github.com/snicoll/
cef801932814a15f35180cc8c173f2a8

>
> > But just change the damn error message ;-)
>
> What's wrong with it? What should be changed?
>

Well, first of all I have no idea what the following means:

rearrange the causing imports in the inheritance hierarchy to apply
standard override logic based on artifact coordinates.

I think the error message has the information but it's a bit too verbose.
Do we really need to give the full location of the pom files? Providing the
"groupId:artifactId:version" coordinates should be enough IMO. And maybe we
could also flip the message so that it is more obvious. Something along the
lines of:

Dependency 'org.springframework.cloud:spring-cloud-commons:jar' has
conflicting dependency management from '
org.springframework.cloud:spring-cloud-consul-dependencies:1.0.2.RELEASE' and
'org.springframework.cloud:spring-cloud-commons-dependencies:1.1.0.RELEASE'

Thanks,
S.




>
> See
> <https://git-wip-us.apache.org/repos/asf?p=maven.git;a=
> blob;f=maven-model-builder/src/main/java/org/apache/
> maven/model/composition/DefaultDependencyManagementImporter.java;h=
> c3a0201b34be6402333f90ed4b807ec62e9ff898;hb=HEAD>
>
>
> Regards,
> --
> Christian
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to