You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Elliotte Rusty Harold (Jira)" <ji...@apache.org> on 2019/12/22 12:59:00 UTC

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

     [ https://issues.apache.org/jira/browse/MRELEASE-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Elliotte Rusty Harold updated MRELEASE-308:
-------------------------------------------
    Priority: Minor  (was: Major)

> Provide an easier way to debug forked Maven process
> ---------------------------------------------------
>
>                 Key: MRELEASE-308
>                 URL: https://issues.apache.org/jira/browse/MRELEASE-308
>             Project: Maven Release Plugin
>          Issue Type: New Feature
>          Components: perform
>            Reporter: Daniel Fabulich
>            Priority: Minor
>
> 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 was sent by Atlassian Jira
(v8.3.4#803005)