[
https://issues.apache.org/jira/browse/SUREFIRE-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101085#comment-16101085
]
ASF GitHub Bot commented on SUREFIRE-1383:
------------------------------------------
GitHub user owenfarrell reopened a pull request:
https://github.com/apache/maven-surefire/pull/157
SUREFIRE-1383 dependenciesToScan Does Not Leverage Classpath Elements
Added logic to prefer output directories of projects built as part of the
current session.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/owenfarrell/maven-surefire master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/maven-surefire/pull/157.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #157
----
commit ee3b5be037c70d2a4667d786d4c487cf89ebfdfa
Author: Owen Farrell <owen.farr...@gmail.com>
Date: 2017-07-26T02:30:52Z
SUREFIRE-1383: Added logic to use build output directories for session
projects in favor of installed artifacts
----
> 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: Backlog
>
> 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.4.14#64029)
