[
https://issues.apache.org/jira/browse/MINVOKER-282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17958438#comment-17958438
]
Olivier Lamy commented on MINVOKER-282:
---------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-invoker-plugin#476|https://github.com/apache/maven-invoker-plugin/issues/476].
> Can't use mvnDebug since Maven 3.8.1
> ------------------------------------
>
> Key: MINVOKER-282
> URL: https://issues.apache.org/jira/browse/MINVOKER-282
> Project: Maven Invoker Plugin (Moved to GitHub Issues)
> Issue Type: Bug
> Reporter: Robert Scholte
> Priority: Critical
>
> The invoker does seem to execute the test, but it is not using mvnDebug (
> {{-Dinvoker.mavenExecutable=mvnDebug}} ) , as if it silently ignored. The
> verbose output shows that mavenExecutable is correctly set to mvnDebug.
> Maven 3.8.1 doesn't contain a lot of changes compared to Maven 3.6.3.
> Possible suspects are merging issues with the new blocked-element or the http
> handling.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
