Home » Newcomers » Newcomers » workspace organization
| workspace organization [message #782398] |
Mon, 23 January 2012 16:47  |
 Marcus Kelvin
Messages: 1
Registered: January 2012 |
Junior Member |
|
|
This is WRT java, but I notice similar issues with the workspace in perl, C, C++, and js.
I'd like to have a folder in my workspace to group related projects together. Since I can't create a top level folder, I used a "project". Inside, the individual projects are in separate source folders. However, they do no require or involve one another. Some of them contain packages and a short demo, usually, Demo.java.
This is a problem because trying to compile one demo after another one results in a "class Demo already exists" error. I've gotten around this by removing all folders from the build path, then adding the one I want to play with back in, but that is a hassle. I've looked at the build path filters, but AFAICT these cannot be used to isolate multiple folders from each other and leave their contents compilable.
What's the answer to all this? I regularly work in several languages simultaneously, I need to be able to organize the workspace so that functional/programmatic relationships can begin somewhere inside a directory tree, but eclipse seems to preclude this -- they are enforced from the top.
|
|
|
| Re: workspace organization [message #782446 is a reply to message #782398] |
Mon, 23 January 2012 17:57  |
|
On 23-Jan-12 09:47, Marcus Kelvin wrote:
> This is WRT java, but I notice similar issues with the workspace in
> perl, C, C++, and js.
> I'd like to have a folder in my workspace to group related projects
> together. Since I can't create a top level folder, I used a "project".
> Inside, the individual projects are in separate source folders. However,
> they do no require or involve one another. Some of them contain packages
> and a short demo, usually, Demo.java.
>
> This is a problem because trying to compile one demo after another one
> results in a "class Demo already exists" error. I've gotten around this
> by removing all folders from the build path, then adding the one I want
> to play with back in, but that is a hassle. I've looked at the build
> path filters, but AFAICT these cannot be used to isolate multiple
> folders from each other and leave their contents compilable.
>
> What's the answer to all this? I regularly work in several languages
> simultaneously, I need to be able to organize the workspace so that
> functional/programmatic relationships can begin somewhere inside a
> directory tree, but eclipse seems to preclude this -- they are enforced
> from the top.
What you're attempting is probably misguided. Use Eclipse Help to
discover how the feature of "Working Set" works.
|
|
|
| Re: workspace organization [message #782509 is a reply to message #782446] |
Mon, 23 January 2012 21:06 |
Eric Rizzo
Messages: 3070
Registered: July 2009 |
Senior Member |
|
|
On 1/23/12 12:57 PM, Russell Bateman wrote:
> On 23-Jan-12 09:47, Marcus Kelvin wrote:
>> This is WRT java, but I notice similar issues with the workspace in
>> perl, C, C++, and js.
>> I'd like to have a folder in my workspace to group related projects
>> together. Since I can't create a top level folder, I used a "project".
>> Inside, the individual projects are in separate source folders. However,
>> they do no require or involve one another. Some of them contain packages
>> and a short demo, usually, Demo.java.
>>
>> This is a problem because trying to compile one demo after another one
>> results in a "class Demo already exists" error. I've gotten around this
>> by removing all folders from the build path, then adding the one I want
>> to play with back in, but that is a hassle. I've looked at the build
>> path filters, but AFAICT these cannot be used to isolate multiple
>> folders from each other and leave their contents compilable.
>>
>> What's the answer to all this? I regularly work in several languages
>> simultaneously, I need to be able to organize the workspace so that
>> functional/programmatic relationships can begin somewhere inside a
>> directory tree, but eclipse seems to preclude this -- they are enforced
>> from the top.
>
> What you're attempting is probably misguided. Use Eclipse Help to
> discover how the feature of "Working Set" works.
I second the recommendation for using Working Sets.
Also consider using multiple workspaces. What you describe really are
separate projects; you're really fighting against Eclipse by trying to
put them all under a single Project. When I have a group of
somehow-related projects, I put them into their own workspace. You can
even have more than one workspace open at a time, as long as your
computer has enough processing power and memory to handle multiple
instances of Eclipse running simultaneously.
Another option that might really serve you well is to utilize the Mylyn
features of Eclipse. Mylyn focuses/filters almost everything in the IDE
based on the notion of Tasks - the currently active Task has a context
associated with it that includes things like what editors are open,
what's visible in the various navigator views, etc. It even coordinates
with Working Sets, too.
Eric
|
|
| |
Goto Forum:
Current Time: Sat Apr 27 04:15:50 GMT 2024
Powered by FUDForum. Page generated in 0.10063 seconds |
] 
Search
Help
Register
Login
Home
