Community
Participate
Working Groups
I20080603-2000 It's possible to build a working set. But to do this, the action 'Project > Build Working Set > YourWorkingSet' needs to be invoked every time. I would expect that Ctrl + B (and even autobuild) can build just a working set. I would suggest to change the UI the following way Build (Ctrl + B) Build Set > o All o MyWorkingSet1 o MyWorkingSet1, MyWorkingSet2 Select Working Sets... The build set specifies what Ctrl + B will do. The entries 'MyWorkingSet1' and 'MyWorkingSet1, MyWorkingSet2' represent a (limited) history of the last selected working sets (Note that you can select more than one working set!) I would also allow that 'Auto build' can just build a build set. This would help users with big workspaces to exclude some less important projects from build. The current UI is, in my opinion, really strange and not very useful.
(In reply to comment #0) > I20080603-2000 > > I would also allow that 'Auto build' can just build a build set. This would > help users with big workspaces to exclude some less important projects from > build. > All good ideas, but this one is made of win. This would be a very helpful feature.
(In reply to comment #1) > All good ideas, but this one is made of win. This would be a very helpful > feature. > So you're going to implement it? Need to understand if this impacts other projects/consumers.
(In reply to comment #2) > (In reply to comment #1) > > All good ideas, but this one is made of win. This would be a very helpful > > feature. > > > So you're going to implement it? > > Need to understand if this impacts other projects/consumers. > I will investigate it for M3. It might not be feasible or it may be prohibitive - the builder is lower than the UI so we need a way to inject into the builder a the things which qualify for autobuilding.
Moving target as M1 has shipped.
Reassigning to new component owners.
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.
