Eclipse Community Forums: Eclipse Platform » Source browsing on java files outside of workspace

Home » Eclipse Projects » Eclipse Platform » Source browsing on java files outside of workspace

Source browsing on java files outside of workspace [message #675795]

Wed, 01 June 2011 10:26

Eclipse User

Hey guys,

We have source code organized into two big workspaces (let's call it A and B). Projects in both workspaces will end up being deployed and running on the same platform. When people develop on projects in workspace A, they also want to be able to do the following thins in the java files in workspace B:
1. Open the source code in workspace B;
2. Use the "Open Type" feature to find classes in workspace B;
3. Find call hierarchy for a certain API from both workspace A and B;

I know in eclipse, we need a java file to be in the workspace or in the classpath to do all those things. Is there any way, e.g. extension point, that we can provide extra search path to eclipse, so that eclipse can do what I said above?

Thanks.

Re: Source browsing on java files outside of workspace [message #675827 is a reply to message #675795]

Wed, 01 June 2011 10:40

Eclipse User

On 01.06.2011 16:26, Raymond wrote:
> Hey guys,
>
> We have source code organized into two big workspaces (let's call it A
> and B). Projects in both workspaces will end up being deployed and
> running on the same platform. When people develop on projects in
> workspace A, they also want to be able to do the following thins in
> the java files in workspace B:
> 1. Open the source code in workspace B;
> 2. Use the "Open Type" feature to find classes in workspace B;
> 3. Find call hierarchy for a certain API from both workspace A and B;
>
> I know in eclipse, we need a java file to be in the workspace or in
> the classpath to do all those things. Is there any way, e.g. extension
> point, that we can provide extra search path to eclipse, so that
> eclipse can do what I said above?
Why don't you combine the projects into one workspace?

Dani
>
> Thanks.
>

Re: Source browsing on java files outside of workspace [message #675855 is a reply to message #675827]

Wed, 01 June 2011 13:48

Eclipse User

We have hundreds projects in total. A developer may only work on some of them. No one wants to have so many projects imported into his workspace.

Re: Source browsing on java files outside of workspace [message #675888 is a reply to message #675855]

Wed, 01 June 2011 16:03

Eclipse User

The features that you are asking about require context. This is why you need to have things in a workspace. The workspace gives context.

Are you aware that you can attach source code to jar files? This allows you to attach the source code to an API jar file you use in one of your projects. You can then open the class and have the source code displayed instead of the class file editor. Having the API jars on a classpath allows you to use the Open Type and find the call hierarchy as well. If the jars aren't needed by any project in your workspace you can even create a project that is essentially just a collection of jar files. You can then import this into your workspace.

Re: Source browsing on java files outside of workspace [message #675958 is a reply to message #675855]

Thu, 02 June 2011 02:50

Eclipse User

On 01.06.2011 19:48, Raymond wrote:
> We have hundreds projects in total. A developer may only work on some
> of them. No one wants to have so many projects imported into his
> workspace.
Well, but on the other hand it seems you need all of them? You could use
working sets to group the projects or even close unrelated projects and
then reopen them when needed.

Another solution could be to use File > Switch Workspace.

Dani

Previous Topic:	Copy/Paste not working in plugin, but in RCP
Next Topic:	Showing an Image while the section is being regenerated in the Background

Goto Forum:

-=] Back to Top [=-

Current Time: Sun Jul 27 23:00:36 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter