You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Hudson (Jira)" <ji...@apache.org> on 2021/11/05 12:17:00 UTC
[jira] [Commented] (MNG-7289) Tests of Forked Execution fails with
Guice provision errors, while unforked succeeds
[ https://issues.apache.org/jira/browse/MNG-7289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17439226#comment-17439226 ]
Hudson commented on MNG-7289:
-----------------------------
Build succeeded in Jenkins: HttpComponents » HttpComponents Website » rework #20
See https://ci-builds.apache.org/job/HttpComponents/job/HttpComponents%20Website/job/rework/20/
> Tests of Forked Execution fails with Guice provision errors, while unforked succeeds
> ------------------------------------------------------------------------------------
>
> Key: MNG-7289
> URL: https://issues.apache.org/jira/browse/MNG-7289
> Project: Maven
> Issue Type: Bug
> Affects Versions: 3.6.3, 4.0.0-alpha-1, 3.8.3
> Reporter: Robert Scholte
> Priority: Critical
>
> When checking out https://github.com/apache/maven-release/commit/6acc4ea3c0b0a011229497c60b99cfebf680d862 and run {{mvn test}} you'll see no issues.
> However, if you run {{mvn site -Preporting}} you'll notice that the maven-surefire-report-plugin starts a fork calling the test phase. Here all tests fail with ComponentLookup error.
> Maven succeeds, probably because it simply generates a report summarying the test results.
> Jenkins on the other hand does detect these failures and makes the build fail.
> For some reason in this case the component descriptors cannot be found. The workaround is to run {{mvn package site -Preporting}}
> Interesting fact: current Maven 4 already fails on module 3 during compilation with {{cannot find symbol}}, I suspect MNG-6566 exposes the root cause earlier.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)