Bug 302867 - Build automatically should be configurable to apply to only a working set, or a set of projects
Summary: Build automatically should be configurable to apply to only a working set, or...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 3.5.1   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Resources-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-15 10:20 EST by Gillis J. de Nijs CLA
Modified: 2019-09-06 16:10 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gillis J. de Nijs CLA 2010-02-15 10:20:36 EST
Build Identifier: 20090920-1017

I recently changed positions within the company.  Although that was a nice change in itself, I still get a lot of questions from my previous department.  As a result, I usually leave the project for that dept open.  For the projects I'm working on now that I moved, I tend to turn on Build Automatically.  However, this will also build my previous projects, although there's really no actual need for that.  I could close the other project, and then open it every time I get a question, but that seems cumbersome.  I'd rather be able to choose what I want to be built automatically when I turn that on.  Every now and then I refresh my entire workspace, so Eclipse will be able to keep up with my automated Subversion Update that runs in the background.  I do not want it to start building my entire workspace, in these cases.  That just takes too much time.

Reproducible: Always

Steps to Reproduce:
1. Turn on build automatically.
2. Notice that all projects get built.
Comment 1 Remy Suen CLA 2010-02-15 10:31:02 EST
This is defined by the workspace's description. The UI just toggles setAutoBuilding(boolean) on the IWorkspaceDescription. We will need Resources to do something first.
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:10:11 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.