slawekjaranowski commented on code in PR #750: URL: https://github.com/apache/maven-invoker-plugin/pull/750#discussion_r3886203578
########## src/site/markdown/examples/debugging.md.vm: ########## @@ -0,0 +1,77 @@ +<!-- +Licensed to the Apache Software Foundation (ASF) under one +or more contributor license agreements. See the NOTICE file +distributed with this work for additional information +regarding copyright ownership. The ASF licenses this file +to you under the Apache License, Version 2.0 (the +"License"); you may not use this file except in compliance +with the License. You may obtain a copy of the License at + +http://www.apache.org/licenses/LICENSE-2.0 + +Unless required by applicable law or agreed to in writing, +software distributed under the License is distributed on an +"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +KIND, either express or implied. See the License for the +specific language governing permissions and limitations +under the License. +--> + +# Debugging Tests + +Sometimes you need to debug an integration test exactly as the Invoker Plugin ran it. Here's how. + +# Using mvnDebug + +Each IT runs in a forked Maven process. The easiest way to attach a JVM debugger to that process is to set the [`mavenExecutable`](../run-mojo.html#mavenExecutable) parameter to `mvnDebug`. Maven ships this script next to `mvn`; it listens for a remote debugger on port 8000 and waits until one attaches. + +```shell +mvn verify -Dinvoker.mavenExecutable=mvnDebug Review Comment: It will execute all ITs with `mvnDebug` each test one by one. In most of case users wants to debug exactly one test. I would like to not proposed it as first step -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
