mockito-inline 3.5.13 depends on core 3.3.3

[Bertold Kolics]

Hi,

[ Excuse me if this is a known issue. I looked in GitHub issue tracker, but I could not find an answer there. ]

I was trying to use the mockito-inline dependency in my project, but it fails maven enforcer plugin rule (RequireUpperBoundDeps), because the published mockito-inline component ( 3.5.13) depends on mockito-core 3.3.3.

Am I reading this right? If so, should I open an issue?

Thank you,

Bertold Kolics

[Tim van der Lippe]

Based on https://repo1.maven.org/maven2/org/mockito/mockito-inline/3.5.13/mockito-inline-3.5.13.pom it seems to depend on mockito-core 3.5.13:

<dependencies>

<dependency>

<groupId>org.mockito</groupId>

<artifactId>mockito-core</artifactId>

<version>3.5.13</version>

<scope>compile</scope>

</dependency>

</dependencies>

Do you have any other transitive dependency on Mockito?

Op zo 4 okt. 2020 om 22:52 schreef Bertold Kolics <ber...@mabl.com>:

--
You received this message because you are subscribed to the Google Groups "mockito" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mockito+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mockito/367d3ba4-afd2-4cea-bfbb-17cd31f14ad5n%40googlegroups.com.

[Bertold Kolics]

Tim,

Thank you for the prompt response. When I run mvn dependency:tree, this is what I see.

[INFO] +- org.mockito:mockito-inline:jar:3.5.13:test
[INFO] |  \- org.mockito:mockito-core:jar:3.3.3:test

I checked my pom, nothing else is referencing core, directly and this dependency shows up at the root of the tree as expected since it is a direct dependency in my project.

The only other problem I can see is that my plugin repositories is using:
    <pluginRepositories>
        <pluginRepository>
            <id>repo.jenkins-ci.org</id>
            <url>https://repo.jenkins-ci.org/public/</url>
        </pluginRepository>
    </pluginRepositories>

But I checked that repo, too. It shows the correct *core* version. So, I am now baffled. Is the Java version could possibly play a role here? Or perhaps the maven version (I am using maven 3.6.3).

Thank you,

Bertold

You received this message because you are subscribed to a topic in the Google Groups "mockito" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/mockito/_aNi1ChEXMc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to mockito+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mockito/CAAYcR_JStQVf2daUy3iACqjpHKfEc%3DHCRUk4ZLs5MDFEKNOkig%40mail.gmail.com.

--

Bertold Kolics
Quality Catalyst
+1.512.226.3605

mabl
www.mabl.com

Mabl Named a Strong Performer in the Forrester Wave^TM:
Continuous Functional Test Automation Suites, Q2 2020

> Get the report <

[Tim van der Lippe]

I honestly don't know :( I guess the Maven resolution algorithm might be at play here?

Op zo 4 okt. 2020 om 23:47 schreef Bertold Kolics <ber...@mabl.com>:

To view this discussion on the web visit https://groups.google.com/d/msgid/mockito/CAF-Me-Fg1a%2Bx7m-%3DfRt3RXO%3DvzEnJi_-Ss5bMmwdoxd%3DDnXcpg%40mail.gmail.com.