[Comment Edited] (SUREFIRE-1390) maven-failsafe-plugin:2.20:verify classNotFound (spring autowired service) testNg

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[Comment Edited] (SUREFIRE-1390) maven-failsafe-plugin:2.20:verify classNotFound (spring autowired service) testNg

JIRA jira@apache.org

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

Tibor Digana edited comment on SUREFIRE-1390 at 7/15/17 12:04 PM:
------------------------------------------------------------------

[~hhwebdev]
I do not think we picked up your class out from classpath. If 2.18 was working I guess it is issue fixed afterwards.
I think it's because Failsafe plugin takes {{*.jar}} file and not {{target/classes}} in to {{Class-Path}}.
Why don't you analyse Clas-Path in Manifest in {{target/surefire/*.jar}} and see what's going on? I do not see your project but I guess {{target/classes}} is not a content what actually appears in your artifact {{jar}}.


was (Author: tibor17):
[~hhwebdev]
I do not think we picked up your class out from classpath. If 2.18 was working I guess it is issue fixed afterwards.
I think it's because Failsafe plugin takes {{*.jar}} file and not {{target/classes}} in to {{Class-Path}}.
Why don't you analyse Clas-Path in Manifest in {{target/surefire/*.jar}} and see what's going on? I do not see your project but I guess {{target/classes}} is not a content what is actually in your artifact {{jar}}.

> maven-failsafe-plugin:2.20:verify classNotFound (spring autowired service) testNg
> ---------------------------------------------------------------------------------
>
>                 Key: SUREFIRE-1390
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1390
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: Maven Failsafe Plugin, TestNG support
>    Affects Versions: 2.19, 2.19.1, 2.20
>         Environment: Win 10; terminal: MINGW64; Spring boot starter [1.5.3, 1.5.4]
>            Reporter: hhwebdev
>              Labels: build, test
>         Attachments: 2017-07-12T09-45-33_517-jvmRun1.dump, cmd_mvn_install_X.txt, failsafe-summary.xml
>
>
> Apologies in advance if duplicate or needs to be in Failsafe specific project, am new to jira, tried searching, but couldn't find match. Not sure if bug in plugin, but couldn't find anything on google/SO based on failsafe stacktrace.
> Upgrading failsafe versions to [2.19, 2.20] causes unexpected failure during integration test run of spring-based testNg tests.
> However, remaining on current failsafe version, 2.18.1, works as expected.
> See attachments for more details.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
Loading...