[
https://issues.apache.org/jira/browse/MINVOKER-282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413749#comment-17413749
]
Slawomir Jaranowski commented on MINVOKER-282:
----------------------------------------------
My test:
{code:java}
$ mvn invoker:run -Dinvoker.streamLogs -Dinvoker.mavenExecutable=mvnDebug
Apache Maven 3.8.2 (ea98e05a04480131370aa0c110b8c54cf726c06f)
Maven home: /usr/local/Cellar/maven/3.8.2/libexec
Java version: 1.8.0_302, vendor: Homebrew, runtime:
/usr/local/Cellar/openjdk@8/1.8.0+302/libexec/openjdk.jdk/Contents/Home/jre
Default locale: en_GB, platform encoding: UTF-8
OS name: "mac os x", version: "10.15.7", arch: "x86_64", family: "mac"
...
[INFO] --- maven-invoker-plugin:3.2.2:run (default-cli) @
sitemapxml-maven-plugin ---
[INFO] Building: site-skip/pom-test.xml
[INFO] Preparing to execute Maven in debug mode
[INFO] Listening for transport dt_socket at address: 8000
...
wait for debuger ...
{code}
seem to work with {{3.8.2}}
> 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)
