[jira] Commented: (MRELEASE-308) Provide an easier way to debug forked Maven process

["nicolas de loof (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MRELEASE-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_117395 ] 

nicolas de loof commented on MRELEASE-308:
------------------------------------------

Same requirement to investigate MRELEASE-271.

The forked mvn instance has a reactor dependencyResolution issue, that will require remote debugging.

> Provide an easier way to debug forked Maven process
> ---------------------------------------------------
>
>                 Key: MRELEASE-308
>                 URL: http://jira.codehaus.org/browse/MRELEASE-308
>             Project: Maven 2.x Release Plugin
>          Issue Type: Improvement
>            Reporter: Dan Fabulich
>
> I was just hit by MRELEASE-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!

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira