[news.eclipse.tools] Re: Java builders and separate projects

["Jeff McAffer" <mcaffer@xxxxxxxx>]

I won't be able to answer all the questions but...
<jamsden@xxxxxxxxxx> wrote in message news:9b75aj$9cg$1@xxxxxxxxxxxxxxxx
> When I have multiple, independent Java projects open in my workspace,
> sometimes a change to a Java file in one project causes the other projects
> to get built even though there are no dependencies. Is this supposed to
> happen?

If you are doing incremental builds (e.g., have autobuild on) then all
project's builders get invoked.  However, unless something actually changed
since the last time a builder ran, no work should be done and you would be
hard-pressed to even tell it was happening.  If you use the "Rebuild"
operations, this will cause all builders to be run as though it was the
first time they had ever run.

>If I close the projects I'm not working on, will this stop this
> rebuilding?

Build only works on open projects so closing a project will stop it from
being built.  Note however that closing a project makes all of the resources
in the project inaccessible.  They effectively do not exist until the
project is reopened.

> What does closing a project mean? Why would I want to keep some closed?

Hmmm, to keep the project from being built?! :-)  Actually, the idea is that
projects you are not using/working on do not need to be open and cluttering
up your work environment.  Much like you would close files in Word once you
are done with them. All this does is save the state of the project and
remove it from the workspace's in-memory model.  This reduces footprint and
may make some operations (e.g., Rebuild) faster.

> If a project built and contributed compilation errors to the task view,
> how can I remove these messages if I'm not working on that project for a
> while?

I know there are filtering/scoping capabilities in the Task list but have
not played in this area too much.  Someone else?

Jeff