Opened 11 years ago
Last modified 5 years ago
#39991 closed enhancement
maven_select not setting up mvnDebug — at Version 2
| Reported by: | genthaler@… | Owned by: | blair@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | ||
| Port: | maven_select |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
Please create symlinks for mvnDebug in a similar way as for mvn.
Currently, I have all 3 mavens installed, and the following symlinks are in place:
/opt/local/bin/mvn -> /opt/local/bin/mvn3 /opt/local/bin/mvn1 -> ../share/java/maven1/bin/mvn /opt/local/bin/mvn2 -> ../share/java/maven2/bin/mvn /opt/local/bin/mvn3 -> ../share/java/maven3/bin/mvn
What's missing from this are symlinks to mvnDebug (which is similar to the mvn command but sets up the appropriate options for JDWP).
Now I could just call mvn -DMAVEN_OPTS=-Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=8000
but that's extra friction.
Thanks.
Change History (2)
comment:1 Changed 11 years ago by genthaler@…
| Cc: | genthaler@… added |
|---|
comment:2 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | genthaler@… removed |
|---|---|
| Description: | modified (diff) |
| Owner: | changed from macports-tickets@… to blair@… |
Note: See
TracTickets for help on using
tickets.
Cc Me!