2011/12/8 Benson Margulies <bimargul...@gmail.com>:
> 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.

Perso I have same issue even with idea :-)
Yup maven ide integration doesn't "override" core dependencies with
your running core.

BTW looks to be an issue with @aggregator and forked lifecycle in
javadoc aggregator mojo.

I recommend you have a look how this forkedLifecycle is calculated.
Various places to investigate are :
* maven-reporting-exec component in shared path
* in core: DefaultLifecycleExecutor especially methods:
calculateForkedExecutions and executeForkedExecutions (that's the
point where javadoc aggregator is executed in case of the site plugin
in 3.x )

HTH

>
>
> On Wed, Dec 7, 2011 at 9:27 PM, Benson Margulies <bimargul...@gmail.com> 
> 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: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



-- 
Olivier Lamy
Talend: http://coders.talend.com
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

Reply via email to