[
https://issues.apache.org/jira/browse/MINVOKER-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated MINVOKER-282:
------------------------------------
Description:
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.
was:
The invoker does seem to execute the test, but it is not using mvnDebug, as if
it silently ignored.
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.
> 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
> Issue Type: Bug
> Reporter: Robert Scholte
> Priority: Critical
> Fix For: 3.3.0
>
>
> 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.3.4#803005)
