maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SUREFIRE-1383) dependenciesToScan Does Not Leverage Classpath Elements
Date Thu, 10 May 2018 03:26:00 GMT

    [ https://issues.apache.org/jira/browse/SUREFIRE-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16469873#comment-16469873
] 

ASF GitHub Bot commented on SUREFIRE-1383:
------------------------------------------

Tibor17 commented on issue #164: SUREFIRE-1383: Split IT569 in to multiple lifecycles
URL: https://github.com/apache/maven-surefire/pull/164#issuecomment-387940764
 
 
   @owenfarrell 
   This feature was merged and will be released in version 2.22.0. You can close the PR.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> 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
>            Assignee: Tibor Digana
>            Priority: Major
>             Fix For: 2.22.0
>
>         Attachments: scanned-dependencies-sample.zip
>
>          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
(v7.6.3#76005)

Mime
View raw message