| Make F3 open Java source from a different project [message #175463] |
Thu, 19 October 2006 08:58  |
Eclipse User |
|
|
|
Platform: Intel Pentium M,
Ubuntu Dapper Drake,
eclipse 3.2
If I have a Java source file in the Java Editor, and then position the
cursor to see the definition of a class that resides in a different
Java project in the same workspace, is it possible to configure
Eclipse to display the source file, instead of the class file?
It's possible to use the JAD plugin to display a decompiled version of
the class file, but I'd rather have the original Java file.
I've also found a way of making the debugger pick up the Java souce
file from other projects, by adding the projects to the "Source Lookup
Path" of the "Source" tab of the run configurations.
But I haven't (yet) found an equivalent setting for the Java editor.
Does anyone know if there is one?
Thanx!
- Steinar
|
|
|
|
| Re: Make F3 open Java source from a different project [message #175658 is a reply to message #175596] |
Thu, 19 October 2006 17:27  |
| Eclipse User |
|
|
|
>>>>> Eric Rizzo <eclipse4@rizzoweb.com>:
> It sounds like your one project includes a JAR of the code from the
> other project (that is why F3 is showing you the .class file). What
> you want to do is make the one project depend on the other project
> directly, not on a JAR. In the Project Properties, Build Path
> section you can edit the Projects tab to include the other
> project. Also make sure to remove the JAR from the Libraries tab.
Both projects are actually OSGi plugin projects, and both projects
results in more than one plugin. They're built using maven, and the
classpath of both projects is maintained by m2eclipse, based on the
POM for the project(s).
But I guess it would be possible to have maven make source JARs, drop
them into the repository, and then, somehow make my project pick them
up...?
|
|
|
Powered by
FUDForum. Page generated in 0.08045 seconds
Home