You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Hodnett (JIRA)" <ji...@apache.org> on 2017/07/12 14:15:00 UTC
[jira] [Updated] (SUREFIRE-1390) maven-failsafe-plugin:2.20:verify
classNotFound (spring autowired service) testNg
[ https://issues.apache.org/jira/browse/SUREFIRE-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Hodnett updated SUREFIRE-1390:
--------------------------------------
Summary: maven-failsafe-plugin:2.20:verify classNotFound (spring autowired service) testNg (was: maven-failsafe-plugin:2.20 classNotFound (spring autowired service) testNg)
> 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: Michael Hodnett
> Labels: build, test
> Fix For: 2.18.1
>
> 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)