Owen Farrell created SUREFIRE-1383:
--------------------------------------
Summary: dependenciesToScan Does Not Leverage Classpath Elements
Key: SUREFIRE-1383
URL: https://issues.apache.org/jira/browse/SUREFIRE-1383
Project: Maven Surefire
Issue Type: Bug
Components: Maven Surefire Plugin
Affects Versions: 2.20
Reporter: Owen Farrell
Fix For: 3.0, 2.20.1
Attachments: scanned-dependencies-sample.zip
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
(v6.3.15#6346)
