[ 
https://jira.codehaus.org/browse/SUREFIRE-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christopher Smith updated SUREFIRE-1094:
----------------------------------------

    Description: 
When using the {{test-jar}} functionality, the {{test}} dependencies declared 
in the test jar are not added to the runner's classpath, leading to 
{{NoClassDefFoundErrors}} (or silent failures to match annotations on any test 
methods) when running the client project. Explicitly declaring a dependency on 
the upstream project does not help. Overriding the dependency scope on the 
upstream's dependencies to {{compile}} causes the client project to resolve the 
dependencies.

I expected the client project to pull in the {{test}} dependencies needed by 
the upstream project when running its tests.

  was:
When using the {{test-jar}} functionality, the {{test}} dependencies declared 
in the test jar are not added to the runner's classpath, leading to 
{{NoClassDefFoundErrors}} (or silent failures to match annotations on any test 
methods) when running the client project. Explicitly declaring a dependency on 
the upstream project does not help.

I expected the client project to pull in the {{test}} dependencies needed by 
the upstream project when running its tests.


> running included tests does not include test dependencies
> ---------------------------------------------------------
>
>                 Key: SUREFIRE-1094
>                 URL: https://jira.codehaus.org/browse/SUREFIRE-1094
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: Maven Failsafe Plugin, Maven Surefire Plugin
>    Affects Versions: 2.17
>            Reporter: Christopher Smith
>
> When using the {{test-jar}} functionality, the {{test}} dependencies declared 
> in the test jar are not added to the runner's classpath, leading to 
> {{NoClassDefFoundErrors}} (or silent failures to match annotations on any 
> test methods) when running the client project. Explicitly declaring a 
> dependency on the upstream project does not help. Overriding the dependency 
> scope on the upstream's dependencies to {{compile}} causes the client project 
> to resolve the dependencies.
> I expected the client project to pull in the {{test}} dependencies needed by 
> the upstream project when running its tests.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

Reply via email to