eclipse features status

Your second question's answer is "this is how eclipse works". The
maven eclipse plugins all have mechanisms to automagicly download/wire
up sources jars.

Unless of course you're talking about stepping through your active
project. In that case, a little more detail would be helpful :)

Sent from my iPhone

On Mar 25, 2009, at 10:30 PM, Naftoli Gugenheim
wrote:

> Hi. I'm using the nightly eclipse plugin.
> How near on the horizon are features like jumping to declaration
> (from source as well as outline) in files that are not in the source
> directory (e.g. library source), finding references (read or write),
> inspecting variables, and call heirachy?
>
> Also, I was trying to debug a Lift app (modified liftone) and I had
> to add the source jars for all the maven dependencies to the source
> lookup path to be able to step through them. Is this a problem with
> the Maven plugin, or the Scala plugin?
>

On Thu, 2009-03-26 at 06:57 -0400, Josh Suereth wrote:
> Your second question's answer is "this is how eclipse works".

This is a bit misleading I think.

> The maven eclipse plugins all have mechanisms to automagicly download/wire
> up sources jars.

Right, so if you configure your system correctly, you won't have to do
it manually (IAM, m2e and mvn eclipse:eclipse all have mechanisms to
download sources and set the source path).

Ismael

On Thu, Mar 26, 2009 at 7:01 AM, Ismael Juma <mlists@juma.me.uk> wrote:

On Thu, 2009-03-26 at 06:57 -0400, Josh Suereth wrote:
> Your second question's answer is "this is how eclipse works".

This is a bit misleading I think.

You are correct, Sir.   However, hopefully my later description recovered.   To formalize, if you want to debug into code inside eclipse, eclipse must be aware of the source code.  For the JDT this usually happens automagically (as well as dependent internal projects).   When using maven, the plugins  can help take care of this.