See https://issues.apache.org/jira/browse/MNG-7215 and the short thread here "Wrong site skin in 3.8.2 vs 3.6.3"
Gary On Fri, Sep 3, 2021, 08:08 Stefan Seifert <stefan.seif...@diva-e.com.invalid> wrote: > i've encountered a problem in numerous of our Maven builds at wcm.io [1] > which started failing yesterday when GitHub switched to latest Maven 3.8.2 > release for their images. > > an example is described in [2], build log [3], to sum it up: > - build fails in when generating the maven site during the javadoc step, > which is unable to find a couple of dependencies which are defined > correctly (they are defined as "provided" in the <dependency> section of > one of the parent POMs) > - the build does not fail when "javadoc:javadoc" is executed directly, > only as part of the "site" goal > - everything runs fine with Maven 3.8.1 or 3.6.3 > > i'm not sure if this is an issue in either site mojo or javadoc mojo or > Maven itself. the release notes [4] contain a pointer to a change around > MNG-6843, but i'm not aware that site or javadoc plugin are spwaning new > threads. > > any ideas about the root cause? > > stefan > > [1] https://github.com/wcm-io > [2] https://wcm-io.atlassian.net/browse/WTOOL-78 > [3] > https://github.com/wcm-io/wcm-io-wcm-core-components/runs/3505611228?check_suite_focus=true > [4] https://maven.apache.org/docs/3.8.2/release-notes.html > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
