I haven't checked, but there is a good chance https://github.com/apache/maven/pull/527 might fix that problem.
Cheers, Falko 03.09.2021 16:02:04 Stefan Seifert <[email protected]>: > thanks for the pointer - but i think my problem is different. in my case it's > not a problem of looking up a site descriptor, but resolving dependencies > from parent POMs during the javadoc generation that is part of the site build. > > i tried the tarball from > https://issues.apache.org/jira/browse/MNG-7218?focusedCommentId=17400589&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17400589 > which reverts the change from MGN-7170, and it fixes the problem with > getting the right skin for the site, but did not fix the problem with the > dependencies in javadoc generation described here initially. > > should i create a new MNG issue for it? > > stefan > >> -----Original Message----- >> From: Gary Gregory <[email protected]> >> Sent: Friday, September 3, 2021 2:41 PM >> To: Maven Developers List <[email protected]> >> Subject: Re: Regression in Maven 3.8.2? site/javadoc generation fails >> >> 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.Seifert@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: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
