[ https://issues.apache.org/jira/browse/MNG-7220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17409991#comment-17409991 ]
Stefan Seifert commented on MNG-7220: ------------------------------------- the ticket [WTOOL-78|https://wcm-io.atlassian.net/browse/WTOOL-78] described a problem with building javadoc as part of a maven site generation that fails due to the problem described in this ticket: - 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 can confirm that the problem is fixed with https://github.com/apache/maven/pull/527 > [REGRESSION] test-classpath incorrectly resolved > ------------------------------------------------- > > Key: MNG-7220 > URL: https://issues.apache.org/jira/browse/MNG-7220 > Project: Maven > Issue Type: Bug > Affects Versions: 3.8.2 > Reporter: Robert Scholte > Priority: Critical > Attachments: 381.log, 382.log > > > The integrationtest of MJAVADOC-259 succeeds with Maven 3.8.1, but fails with > 3.8.2. > Git bisect identifies 76d5f0d942f52650d3bdf775b6af42d23d69066b as the first > bad commit -- This message was sent by Atlassian Jira (v8.3.4#803005)