maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (SUREFIRE-1383) dependenciesToScan Does Not Leverage Classpath Elements
Date Wed, 27 Sep 2017 17:04:00 GMT


ASF GitHub Bot commented on SUREFIRE-1383:

Github user Tibor17 commented on the issue:
    Yeah, I have released 2.20.1 and I had to postpone this issue for 2.21.1.
    OOM was fixed in 2.20.1 and users could not wait longer. This included Java9 support.
    Java 9 is out and I want to release Surefire 2.21.0.Jigsaw in next few days which has
higher priority.
    And then Surefire 2.21.1 is planed for your and other pull request fixed as well.
    Then 2.21.2 will fix a blocker issue, and then we will concentrate on 3.0.0.M1 and JUnit5.
    So this is my plan.

> dependenciesToScan Does Not Leverage Classpath Elements 
> --------------------------------------------------------
>                 Key: SUREFIRE-1383
>                 URL:
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: Maven Surefire Plugin
>    Affects Versions: 2.20
>            Reporter: Owen Farrell
>            Assignee: Tibor Digana
>             Fix For: 2.21.1
>         Attachments:
>          Time Spent: 48h
>  Remaining Estimate: 24h
> The <dependenciesToScan> configuration attribute relies solely on installed artifacts.
This is an issue when the targeted dependencies were built as part of the current session.
The net result is that stale artifacts are used (i.e. if the dependency has changed since
it was last installed) or the tests are not executed at all (if the dependency has not been
previously installed.
> Attached is a sample project that illustrates this issue:
> Given I have a multi-module project
>    And the first module built includes test classes as part of the project artifact
>    And subsequent modules scan the first for unit tests to execute
> When I execute the _*test*_ goal (prior to any install)
> Then the build should succeed
>    And tests should be executed with each module

This message was sent by Atlassian JIRA

View raw message