[jira] [Closed] (MSITE-963) Delete broken site descriptor files from local repository

["Michael Osipov (Jira)" <ji...@apache.org>]

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

Michael Osipov closed MSITE-963.
--------------------------------
    Resolution: Fixed

Fixed with [d452e4befc21c79b12c1277beab975418bca6bc8|https://gitbox.apache.org/repos/asf?p=maven-site-plugin.git;a=commit;h=d452e4befc21c79b12c1277beab975418bca6bc8].

> Delete broken site descriptor files from local repository
> ---------------------------------------------------------
>
>                 Key: MSITE-963
>                 URL: https://issues.apache.org/jira/browse/MSITE-963
>             Project: Maven Site Plugin
>          Issue Type: Sub-task
>            Reporter: Michael Osipov
>            Assignee: Michael Osipov
>            Priority: Major
>
> When you run:
> {noformat}
> rm -rf /tmp/repo1
> mvn clean site -Dmaven.repo.local=/tmp/repo1
> mvn clean verify -Prun-its -Dinvoker.parallelThreads=8  -Dmaven.repo.local=/tmp/repo1
> {noformat}
> these ITs always fail:
> {noformat}
> [ERROR] * effective-site/pom.xml
> [ERROR] * full-reporting/pom.xml
> {noformat}
> The first run places pseudo site descriptor marker files. During ITs MRM Maven Plugin uses the local repo as source for remote repo and delivers 0-byte files. Resolver goes out to fetch those. Subsequent runs with ITs then fail.
> So the only viable way I see is to delete those files first then run the ITs until all is using Maven Site Plugin 4.



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