simon,
been using maven since 2005 so 1.x something, so might be better way
as often i discover features added several releases ago that i simply
missed to kept using the old approach as it works and isn't broken.
Something like;
<project>
...
<profiles>
...
<profile>
<id>debug</id>
<properties>
<project.debug.port>5005</project.debug.port>
<project.debug.args>-agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=${project.debug.port}</project.debug.args>
</properties>
</profile>
...
</profiles>
...
<properties>
....
<argLine>${project.debug.args}</argLine>
....
</properties>
</project>
then "mvn -Pdebug test" and surefire uses the argLine user property.
then if you want to change the port "mvn -Pdebug
-Dproject.debug.port=8000 test". the important part is suspend=y.
Reading the latest
https://maven.apache.org/surefire/maven-surefire-plugin/examples/debugging.html,
then "mvn -Dmaven.surefire.debug test" should setup a debug port on
5005 but i've only just seen that in the latest documentation but i've
probably not looked at surefire documentation for debugging for maybe
6+ years.
John
On Fri, 12 Oct 2018 at 20:25, Simon Sheng <simonshe...@gmail.com> wrote:
>
> Hi John,
>
> I am trying the profile, but no matter 5005 or 8000 port, I can't start
> debug. Would you please give me more detail of this profile.
>
> I global search maven source code, only classworld pom file has debug
> profile.
>
> I am looking into the wrapper you mentioned.
>
> Thank you!
>
> Simon(ChengHong) Sheng
>
>
> On Tue, Oct 9, 2018 at 5:24 AM John Patrick <nhoj.patr...@gmail.com> wrote:
>
> > others have talked about mvnDebug, i prefer using a profile e.g.
> > debug, then all the surefire and failsafe and exec-maven-plugin, plus
> > other plugins are all configured to use ${DEBUG_ARGS}, then;
> >
> > $ mvn -Pdebug test
> > $ mvn -Pdebug exec:java
> >
> > Then in intellij/eclipse/netbeans I can just connect a remote debugger
> > to the code. For some situations you want it to pause the execute
> > until your debugger is connected otherwise you might miss breakpoints
> > if those test are executed 1st.
> >
> > I've also switched to maven wrapper so don't have mvnDebug anymore as
> > it means developers don't need to keep their local machines in sync
> > and just do mvnw and it will sort out the maven version that
> > project/branch requires.
> >
> >
> > On Tue, 9 Oct 2018 at 06:29, Tibor Digana <tibordig...@apache.org> wrote:
> > >
> > > In IntelliJ IDEA it is "Remote", see Select Run/Debug Configurations >
> > > Remote, change the port to 8000.
> > > Run command *mvnDebug test* and then start "Remote" in IDEA.
> > >
> > > On Tue, Oct 9, 2018 at 6:16 AM Romain Manni-Bucau <rmannibu...@gmail.com
> > >
> > > wrote:
> > >
> > > > Hello
> > > >
> > > > Not sure the question was about test classes - you got answers for
> > that ;)
> > > > - or maven and plugins themselves. If the last one, just replace "mvn"
> > by
> > > > "mvnDebug" in any command and remote debug on port 8000 in your IDE.
> > > >
> > > > Side note: if you check mvn script you will see maven has a main class
> > so
> > > > can be remote debugged as any java software ;)
> > > >
> > > > Le mar. 9 oct. 2018 05:44, Olivier Lamy <ol...@apache.org> a écrit :
> > > >
> > > > > an other option is to use command line and the surefire option:
> > > > > -Dmaven.surefire.debug=true
> > > > > then you can have debug on port 5005 (look at your ide to start a
> > remote
> > > > > debug)
> > > > >
> > > > > On Tue, 9 Oct 2018 at 08:45, Enrico Olivelli <eolive...@gmail.com>
> > > > wrote:
> > > > >
> > > > > > Il lun 8 ott 2018, 23:23 Jeff MAURY <jeffma...@gmail.com> ha
> > scritto:
> > > > > >
> > > > > > > M2e takes care of everything
> > > > > > >
> > > > > >
> > > > > > Same for Apache Netbeans :)
> > > > > >
> > > > > > Enrico
> > > > > >
> > > > > >
> > > > > > > Jeff
> > > > > > >
> > > > > > > Le lun. 8 oct. 2018 à 23:09, Simon Sheng <simonshe...@gmail.com>
> > a
> > > > > > écrit :
> > > > > > >
> > > > > > > > Hi,
> > > > > > > >
> > > > > > > > I am bringing this baby question since Maven load all it's
> > classes
> > > > by
> > > > > > > > ClassWorlds. Which means it doesn't have "main method".
> > instead we
> > > > > > debug
> > > > > > > > everything by log, do we have other way like debug with any
> > IDE:
> > > > > > Eclipse,
> > > > > > > > Intellij etc. put breakpoints and debug step by step ?
> > > > > > > >
> > > > > > > > Thanks
> > > > > > > >
> > > > > > > > Simon(ChengHong) Sheng
> > > > > > > >
> > > > > > >
> > > > > > --
> > > > > >
> > > > > >
> > > > > > -- Enrico Olivelli
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Olivier Lamy
> > > > > http://twitter.com/olamy | http://linkedin.com/in/olamy
> > > > >
> > > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
