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

Odne Hellebø edited comment on MNG-7358 at 12/11/21, 8:54 PM:
--------------------------------------------------------------

[~michael-o] I'm not the one choosing the server=y flag, it is there by default 
when I set up the profile to debug things from the commandline. And it worked 
with maven 3.8.3. 

What I do.
1. Do {code:bash}mvnDebug test{code} in terminal, and see that it immediately 
waits (this is different from mvn 3.8.3 which seems to do a bit of work before 
it waits)
2. Go to intellij -> Run -> Debug
3. The code in terminal starts running again, with 3.8.3 it stops at the 
breakpoints, with 4.0.0 it just finishes the program.

I tested in eclipse 2020.3 and I could see the same thing there.


was (Author: JIRAUSER281453):
[~michael-o] I'm not the one choosing the server=y flag, it is there by default 
when I set up the profile to debug things from the commandline. And it worked 
with maven 3.8.3. 

What I do.
1. Do 
{code:bash}
mvnDebug test
{code} in terminal, and see that it immediately waits (this is different from 
mvn 3.8.3 which seems to do a bit of work before it waits)
2. Go to intellij -> Run -> Debug
3. The code in terminal starts running again, with 3.8.3 it stops at the 
breakpoints, with 4.0.0 it just finishes the program.

I tested in eclipse 2020.3 and I could see the same thing there.

> Can't debug with mvnDebug with version 4
> ----------------------------------------
>
>                 Key: MNG-7358
>                 URL: https://issues.apache.org/jira/browse/MNG-7358
>             Project: Maven
>          Issue Type: Bug
>          Components: Command Line
>    Affects Versions: 4.0.x-candidate
>         Environment: Linux
> 3.8.3
> $ mvn --version
> Picked up _JAVA_OPTIONS:  -Dawt.useSystemAAFontSettings=on -Dswing.aatext=true
> Apache Maven 3.8.3 (NON_CANONICAL)
> Maven home: /opt/maven
> Java version: 1.8.0_292, vendor: Oracle Corporation, runtime: 
> /usr/lib/jvm/java-8-openjdk/jre
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "linux", version: "5.15.5-arch1-1", arch: "amd64", family: "unix"
> 4.0.0
> Picked up _JAVA_OPTIONS:  -Dawt.useSystemAAFontSettings=on -Dswing.aatext=true
> Apache Maven 4.0.0-alpha-1-SNAPSHOT (3a06530dbce82e2054afa3cc4c81631910474bd0)
> Maven home: /opt/maven-git
> Java version: 1.8.0_292, vendor: Oracle Corporation, runtime: 
> /usr/lib/jvm/java-8-openjdk/jre
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "linux", version: "5.15.5-arch1-1", arch: "amd64", family: "unix"
>            Reporter: Odne Hellebø
>            Priority: Minor
>         Attachments: intellijDebug.png, mvnDebugGit.zip
>
>
> When using mvnDebug at version 4, it just skips all the breakpoints in 
> intellij.
> These are the settings in intellij
>  !intellijDebug.png! 
> To reproduce just set some breakpoints in test, and then run
> mvnDebug test



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to