[MRELEASE-308] Provide an easier way to debug forked Maven process

**[Daniel Fabulich](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=dfabulich)** opened **[MRELEASE-308](https://issues.apache.org/jira/browse/MRELEASE-308?redirect=false)** and commented

I was just hit by MRELEA[SE-307](https://issues.apache.org/jira/browse/SE-307); the only way to diagnose it was to debug the forked Maven. But the release plugin provides no way to pass debug arguments to the forked Maven.

To debug it, I ultimately had to symlink "mvn" to "mvnDebug" and launch the process with "mvnNoDebug release:perform"; when it went to invoke "mvn" it halted and waited for me to attach.

There must be a better way!

---

**Issue Links:**
- [MSHARED-251](https://issues.apache.org/jira/browse/MSHARED-251) Option to change from mvn executable to mvnDebug executable

1 votes, 1 watchers

Start by reading MRELEASE-308 and the linked MSHARED-251 issue to understand the existing forked Maven invocation and proposed executable option. Done means the release plugin provides a documented way to pass debug arguments to the forked Maven process.

Written by the indexing model from the issue text.