[
https://issues.apache.org/jira/browse/SUREFIRE-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101084#comment-16101084
]
ASF GitHub Bot commented on SUREFIRE-1383:
------------------------------------------
Github user owenfarrell commented on the issue:
https://github.com/apache/maven-surefire/pull/157
And I got busy with other work as well. I think I found a solution that
doesn't completely violate the pattern used by integration tests.
Long story short, the IT for SUREFIRE-569 has been updated to be completely
independent modules. The first module leverages the flatten plugin to avoid any
parent references, which then allows the second module to complete successfully.
The IT for SUREFIRE-1383 executes within a single process and verifies the
updates that I've proposed.
Sorry for all the noise on the ticket - I hosed my fork while making the
last round of updates.
> 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)
