> 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?