Are you running Maven from the IDE, or using the "mvnDebug" remote debugging?
If you have the Maven projects open, and then attach to a Maven process built from those sources, you should be able to trace into them instead - or at least set a breakpoint in there. Been ages since I used Eclipse though, so not sure if that's still valid there. On 08/12/2011, at 10:34 PM, Benson Margulies wrote: > I want to see if I can chase MNG-5214 to its lair. I need a little bit > of coaching to get the debugging process going. > > In the test case, there's a maven plugin which declares various maven > 2 components as provided dependencies, notably the > DefaultArtifactResolver. So, my IDE keeps trying (I think) to show me > the source to the 2.2.1 version even though, since I'm running M3, I'm > using the M3 version. I'm suspecting that you core spelunkers can tell > me how to get Eclipse unconfused. If there's a doc, please point me at > it. If there isn't, please clue me in, and I'll write it. > > > On Wed, Dec 7, 2011 at 9:27 PM, Benson Margulies <[email protected]> > wrote: >> MSITE-623 describes the situation, but, in fact, it's not MSITE at all. >> >> In the case at hand, the artifact resolver is returning the current >> target/classes pathname that goes with the 'jar' artifact as the >> answer to a question about the 'wsdl' artifact. Maven 2.2.1 does fine. >> >> Where do I start? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -- Brett Porter [email protected] http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
