maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tibor Digana (Jira)" <>
Subject [jira] [Closed] (SUREFIRE-1694) Surefire silently skips tests in presence of transitive dependency
Date Tue, 28 Apr 2020 22:26:00 GMT


Tibor Digana closed SUREFIRE-1694.
      Assignee: Tibor Digana
    Resolution: Invalid

No reproducible project and no reply from the user.

> Surefire silently skips tests in presence of transitive dependency
> ------------------------------------------------------------------
>                 Key: SUREFIRE-1694
>                 URL:
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: Maven Surefire Plugin
>    Affects Versions: 2.22.2
>            Reporter: Allen Evans
>            Assignee: Tibor Digana
>            Priority: Blocker
> In a multi-module project, one module "functional-tests" contains a test suite that tests
the whole application.
> Usually, running mvn verify will run the tests in this module.
> {code:java}
> [INFO] --- maven-surefire-plugin:2.22.0:test (default-test) @ functional-tests ---
> [WARNING] file.encoding cannot be set as system property, use <argLine>-Dfile.encoding=...</argLine>
> [INFO]
> [INFO] -------------------------------------------------------
> [INFO]  T E S T S
> [INFO] -------------------------------------------------------
> ...{code}
> Recently, I added a dependency (io.vertx:vertx-config-git) to the pom.xml of one of my
project's modules "config", and now mvn verify breezes through the functional-tests module
without running any of the tests, and without logging anything noteworthy (even with the -X
> {code:java}
> [INFO] --- maven-surefire-plugin:2.22.0:test (default-test) @ functional-tests ---
> [INFO]
> [INFO] --- maven-dependency-plugin:2.8:copy-dependencies (copy-dependencies) @ functional-tests
> ...{code}
> After adding a dependency:exclusion tag to the pom.xml of the "config" module that excludes
a particular transitive dependency from vertx-config-git (org.eclipse.jgit:org.eclipse.jgit),
the tests work as before. Obviously this is not a solution, but it seems to narrow down the
> Is it likely that my issue is caused by the presence of org.eclipse.jgit in my dependency
tree? This seems counterintuitive.

This message was sent by Atlassian Jira

View raw message