Uploaded image for project: 'Maven Release Plugin'
  1. Maven Release Plugin
  2. MRELEASE-308

Provide an easier way to debug forked Maven process

    XMLWordPrintableJSON

Details

    • New Feature
    • Status: Open
    • Minor
    • Resolution: Unresolved
    • None
    • None
    • perform
    • None

    Description

      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!

      Attachments

        Issue Links

          relates to

          Improvement - An improvement or enhancement to an existing feature or task. MSHARED-251 Option to change from mvn executable to mvnDebug executable

          • Major - Major loss of function.
          • Closed

          Activity

            People

              Unassigned Unassigned
              dfabulich Daniel Fabulich
              Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: