Fwd: Unexpected behavior in maven

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Fwd: Unexpected behavior in maven

Enrico Olivelli
---------- Forwarded message ---------
Da: Enrico Olivelli <[hidden email]>
Date: Gio 23 Gen 2020, 14:01
Subject: Re: Unexpected behavior in maven
To: Oleg Kiktev <[hidden email]>
Cc: <[hidden email]>


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 <[hidden email]> 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
>