Bug 441169 - Support nested working sets (AggregateWorkingSet)
Summary: Support nested working sets (AggregateWorkingSet)
Status: CLOSED DUPLICATE of bug 296968
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.5   Edit
Hardware: PC Linux
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 441165
  Show dependency tree
 
Reported: 2014-08-05 08:11 EDT by Ivica Loncar CLA
Modified: 2014-08-05 10:47 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ivica Loncar CLA 2014-08-05 08:11:19 EDT 
JDT at them moment does not support nested working sets (AggregateWorkingSets). This feature is really nice one to have when one has a lot of nested maven or gradle projects.

Right now we have flat project organization as well as flat working set organization. While I understand it's not trivial to support nested projects, could we at least have support for nested working sets?
Comment 1 Dani Megert CLA 2014-08-05 08:49:40 EDT 

*** This bug has been marked as a duplicate of bug 296968 ***
Comment 2 Ivica Loncar CLA 2014-08-05 10:08:06 EDT 
Just out of curiosity: why did you close this bug against JDT? AFAICT JDT has it's internal implementation that explicitly checks for AggregateWorkingSet and disables it in project explorer.
Comment 3 Dani Megert CLA 2014-08-05 10:11:09 EDT 
(In reply to Ivica Loncar from comment #2)
> Just out of curiosity: why did you close this bug against JDT? AFAICT JDT
> has it's internal implementation that explicitly checks for
> AggregateWorkingSet and disables it in project explorer.

Because this is a general (not just JDT) issue which is captured by bug  bug 296968.
Comment 4 Ivica Loncar CLA 2014-08-05 10:19:18 EDT 
Hi Dani 

I'm not that familiar with the way eclipse deals with issue reports so please bear with me.

Wouldn't this information be lost? ie. it would be fixed in platform but the code in JDT would stay the same (ie. effectively disable nested working sets)
Shouldn't it stay open under JDT and added under "depends on" instead?
Comment 5 Dani Megert CLA 2014-08-05 10:21:37 EDT 
(In reply to Ivica Loncar from comment #4)
> Wouldn't this information be lost?

Nothing is lost. This bug is marked as duplicate. When fixing the other bug we check that the duplicates are working.
Comment 6 Ivica Loncar CLA 2014-08-05 10:47:34 EDT 
Ok, thank you.