You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Andreas Pabst (Jira)" <ji...@apache.org> on 2023/02/11 22:34:00 UTC

[jira] [Updated] (SUREFIRE-2149) Several ITs fail with Maven 3.9.0

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

Andreas Pabst updated SUREFIRE-2149:
------------------------------------
    Summary: Several ITs fail with Maven 3.9.0  (was: Several Surefire772*ITs fail with Maven 3.9.0)

> Several ITs fail with Maven 3.9.0
> ---------------------------------
>
>                 Key: SUREFIRE-2149
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-2149
>             Project: Maven Surefire
>          Issue Type: Task
>    Affects Versions: 3.0.0-M8
>            Reporter: Andreas Pabst
>            Priority: Major
>              Labels: build, integration-tests
>
> See errors in continuous build since the switch to Maven 3.9.0
> {noformat}
> Error:  Failures: 
> Error:    Surefire772BothReportsIT.testReportGeneration:57 Expecting failsafe report file
> Error:    Surefire772BothReportsIT.testSkippedSurefireReportGeneration:85 Expecting failsafe report file
> Error:    Surefire772NoSurefireReportsIT.testOptionalSurefireReportGeneration:75 Expecting failsafe report file
> Error:    Surefire772NoSurefireReportsIT.testReportGeneration:49 Expecting failsafe report file
> Error:    Surefire772NoSurefireReportsIT.testSkipOptionalSurefireReportGeneration:88 Expecting failsafe report file
> Error:    Surefire772NoSurefireReportsIT.testSkippedSurefireReportGeneration:62 Expecting failsafe report file
> {noformat}
> The reason is that {{org.apache.maven.surefire.its.fixture.MavenLauncher#skipClean}} still uses the pre-3.0.0 name of the respective {{maven-clean-plugin}} property.
> Before maven-clean-plugin: 
> It should use {{-Dmaven.clean.skip=true}}, not {{-Dclean.skip=true}}
> Maven 3.9.0 uses {{maven-clean-plugin}} in version 3.2 by default. Before it was version 2.5 which was still expecting the old property.
> Fixing this of course means that these ITs will fail with older Maven versions.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)