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

["Guoxiong Li (Jira)" <ji...@apache.org>]

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

Guoxiong Li commented on MNG-7075:
----------------------------------

In the past, when I was only a maven user, I never use the command `mvnDebug`. So if I want to read the version or help infomation, I used `mvn -v` or `mvn -h`. Actually, I don't know that maven has the command `mvnDebug`.

Recently, when I want to dive into maven source code and want to become a maven developer, I used `mvnDebug -version` to debug so that I can see how maven starts and how maven resolves the config. Then, I created a demo maven project and used `mvnDebug clean compile` to debug so that I can see how maven executes the plugins.

Because I had experienced in shell, I tried to read the shell scripts `bin/mvn` and `bin/mvnDebug` so that I can learn more about the maven. But if someone who only know java but don't know anything about shell, he/she can't understand the shell scripts and can only get the meaning of the shell scripts from its name.

So I think `run is run, debug is debug`. We shouldn't add some run cases into the debug situation, which would confuse both users and new developers.

> Let's put it on the mailinglist to see how others think about it.

Could you please point out the mailinglist link about this for me? Thanks a lot.

> 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
>
>
> {{$ 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)