Re: 'Get thee to the core' a concrete opportunity

2011-12-12 Thread Benson Margulies
On Mon, Dec 12, 2011 at 8:01 PM, Brett Porter wrote: > On 10/12/2011, at 9:44 AM, Benson Margulies wrote: > >> On the substance of the original problem: >> >> user runs 'mvn site:site' >> >> site:site finds javadoc and checkstyle, trigger a forked lifecycle to >> generate sources. >> >> In this pa

Re: 'Get thee to the core' a concrete opportunity

2011-12-12 Thread Brett Porter
On 10/12/2011, at 9:44 AM, Benson Margulies wrote: > On the substance of the original problem: > > user runs 'mvn site:site' > > site:site finds javadoc and checkstyle, trigger a forked lifecycle to > generate sources. > > In this particular case, 'generate-sources' in module 'b' depends on > r

Re: 'Get thee to the core' a concrete opportunity

2011-12-09 Thread Benson Margulies
On the substance of the original problem: user runs 'mvn site:site' site:site finds javadoc and checkstyle, trigger a forked lifecycle to generate sources. In this particular case, 'generate-sources' in module 'b' depends on running out through 'process-classes' in module 'a'. b has a compile-s

Re: 'Get thee to the core' a concrete opportunity

2011-12-09 Thread Jesse Glick
On 12/08/2011 06:34 AM, Benson Margulies wrote: 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 run

Re: 'Get thee to the core' a concrete opportunity

2011-12-09 Thread Benson Margulies
Olivier, You're pointing at the original problem: that process-classses doesn't get included in the forked lifecycle. I'm trying to start with the second problem: that the resolver gives a bogus answer. --benson On Thu, Dec 8, 2011 at 11:05 AM, Olivier Lamy wrote: > 2011/12/8 Benson Margulies

Re: 'Get thee to the core' a concrete opportunity

2011-12-09 Thread Benson Margulies
Brett, What are you debugging in these days? On Thu, Dec 8, 2011 at 12:31 PM, Brett Porter wrote: > 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

Re: 'Get thee to the core' a concrete opportunity

2011-12-08 Thread Brett Porter
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 t

Re: 'Get thee to the core' a concrete opportunity

2011-12-08 Thread Olivier Lamy
2011/12/8 Benson Margulies : > 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 > DefaultArtifactRes

'Get thee to the core' a concrete opportunity

2011-12-08 Thread Benson Margulies
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)