[jira] [Comment Edited] (MNG-7075) mvnDebug should only enter debug mode if not an informative or encryption switch has been passed

["Michael Osipov (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MNG-7075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17387488#comment-17387488 ] 

Michael Osipov edited comment on MNG-7075 at 7/26/21, 4:59 PM:
---------------------------------------------------------------

That's correct and I had the very same thought.

I have a completely different, radical idea how to solve it: Get rid of {{mvnDebug}} and collapse it into {{mvn}}. The idea is to add th the CLI parser {{\-\-debug-java}}, {{--dj}}, or similar, but the start scripts would loop through args and detect this switch and start java command with debug flags. No need for {{mvnDebug}} and {{\-\-debug-java -v}} would still work since one deliberately says: debug the process and enable version information.
If this works, We can leave {{mvnDebug}} as-is and add a warning that this script is deprecated and one shall use the alternative.

WDYT?


was (Author: michael-o):
That's correct and I had the very same thought.

I have a completely different, radical idea how to solve it: Get rid of {{mvnDebug}} and collapse it into {{mvn}}. The idea is to add th the CLI parser {{--debug-java}}, {{--dj}}, or similar, but the start scripts would loop through args and detect this switch and start java command with debug flags. No need for {{mvnDebug}} and {{--debug-java -v}} would still work since one deliberately says: debug the process and enable version information.
If this works, We can leave {{mvnDebug}} as-is and add a warning that this script is deprecated and one shall use the alternative.

WDYT?

> mvnDebug should only enter debug mode if not an informative or encryption switch has been passed
> ------------------------------------------------------------------------------------------------
>
>                 Key: MNG-7075
>                 URL: https://issues.apache.org/jira/browse/MNG-7075
>             Project: Maven
>          Issue Type: New Feature
>          Components: Bootstrap & Build
>            Reporter: Paul Hammant
>            Assignee: Michael Osipov
>            Priority: Minor
>             Fix For: 4.0.x-candidate, 3.8.x-candidate
>
>
> {{$ mvnDebug --version }}{{Preparing to execute Maven in debug mode}}{{Listening for transport dt_socket at address: 8000}}
> Should really only spit out the same info as:
> {{$ mvn --version }}{{Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)}}{{Maven home: /usr/local/Cellar/maven/3.6.3_1/libexec}}{{Java version: 11.0.9, vendor: Oracle Corporation, runtime: /Library/Java/JavaVirtualMachines/jdk-11.0.9.jdk/Contents/Home}}{{Default locale: en_US, platform encoding: UTF-8}}{{OS name: "mac os x", version: "10.14.6", arch: "x86_64", family: "mac"}}
> In other words {{mvnDebug }}should *not* listen on the remote debugger port in this {{ --version}}{{ usage}}
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)