Bringing in the source should be a function of your editor. What are you using? It works fine for me in IntelliJ
- Russ On Nov 5, 2013, at 6:09 PM, Steve Cohen <sco...@javactivity.org> wrote: > On 11/05/2013 04:22 PM, Olivier Lamy wrote: >> Use mvnDebug cli instead of mvn >> >> -- >> Olivier >> On Nov 6, 2013 8:09 AM, "Steve Cohen" <sco...@javactivity.org> wrote: >> >>> I have a need to debug the maven-assembly-plugin which is not functioning >>> correctly. I have found the instructions for setting up a debugging >>> environment for maven itself within eclipse. >>> >>> What is the best way to get the source for this plugin so that it can be >>> used by the debugging process. I know I can download it from svn, and >>> attach in Eclipse, but is there a maven command to do that? >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >>> For additional commands, e-mail: users-h...@maven.apache.org >>> >>> >> > Thanks, I am using the mvnDebug cli. That does seems to bring in the Maven > (core and plugin source) but it does not bring in the source for the Codehaus > Plexus stuff called by the plugin, which I also need to see for this > debugging. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > ----------------- Author, Getting Started with Apache Maven <http://www.packtpub.com/getting-started-with-apache-maven/video> Come read my webnovel, Take a Lemon <http://www.takealemon.com>, and listen to the Misfile radio play <http://www.fuzzyfacetheater.com/misfile/>!
