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 Tue, 04 Jul 2017 09:50:00 GMT


ASF GitHub Bot commented on SUREFIRE-1383:

Github user Tibor17 commented on the issue:
    Would you add integration test?
    See the module `surefire-integration-tests` and `src/test/java/org/apache/maven/surefire/its/jiras`.
    It's easy. Pickup some existing test, e.g. `Surefire34SecurityManagerIT`, and just inherit
`SurefireJUnit4IntegrationTestCase`and see the folder `surefire-34-securityManager` in `test/resources`.
    Your IT will have the same principle. The point is to start `surefire-34-securityManager/pom.xml`
as embedded or forked maven process from `Surefire34SecurityManagerIT`. I guess you want to
test that multi-module Maven project will have own classes propagated from child modules one
one dedicated module where Surefire has tests.

> 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
>             Fix For: Backlog
>         Attachments:
> 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