[prev in list] [next in list] [prev in thread] [next in thread] 

List:       maven-user
Subject:    Fwd: Unexpected behavior in maven
From:       Enrico Olivelli <eolivelli () gmail ! com>
Date:       2020-01-23 13:06:11
Message-ID: CACcefgcCNj7C9Qrgf9g_yAc60_gLy6jG428TuHaHvAyA5NJtXQ () mail ! gmail ! com
[Download RAW message or body]


---------- Forwarded message ---------
Da: Enrico Olivelli <eolivelli@gmail.com>
Date: Gio 23 Gen 2020, 14:01
Subject: Re: Unexpected behavior in maven
To: Oleg Kiktev <oleg.kiktev@gmail.com>
Cc: <user@maven.apache.oeg>


Oleg
Do you Havel this problemi in your IDE or even using Maven from the command
line?
What does dependency:tree report?


Enrico

Il Gio 23 Gen 2020, 10:31 Oleg Kiktev <oleg.kiktev@gmail.com> ha scritto:

> Hi Maven Team,
>
> I faced with some strange behavior in maven recently.
> Here are details:
> I have a project with one scope test dependency (D1). Then I added new
> dependency D2 which has the same dependency D1. But for D2 the D1 is needed
> for runtime. Currently maven rejects D1 from D2 and my application does not
> work because required library D2 has been rejected.
>
> On my point of view this is stupid. The test scope of my project
> overwrites compile scope of third-party. And I'm not able to even run
> application in my IDE (Tried Eclipse and intellij).
>
> So could someone explain is it expected behavior or a bug?
>
> Regards,
> Oleg
>


[prev in list] [next in list] [prev in thread] [next in thread]