Bug 301092 - Support 'new resource' decoration for elements that don't adapt to a single resource
Summary: Support 'new resource' decoration for elements that don't adapt to a single r...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.5.1   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-28 02:48 EST by Vladimir Piskarev CLA
Modified: 2019-09-06 16:09 EDT (History)
0 users

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 Vladimir Piskarev CLA 2010-01-28 02:48:50 EST 
Build Identifier: M20090917-0800

Currently, 'new resource' decoration is only supported for elements that adapt to a single resource. Elements that don't have one-to-one correspondence with resources are always decorated as 'remote'. CVSLightweightDecorator has a 'TODO' regarding that (line 210).

The always-remote decoration may be not very intuitive for users. Suppose there is a 'Forms' logical container element that contains all the *.form files in a folder. If all these files are 'new' it seems more appropriate to decorate the container element as 'new', not as 'remote'. This is especially easy to see when the folder itself is also 'new', since it would be strange to have a child 'remote' element ('Forms') under the parent 'new' element (the folder) in a viewer.

A possible solution would be to decorate the logical model element as 'new' if (and only if) all the resources that constitute the element are 'new'.

Reproducible: Always
Comment 1 Eclipse Webmaster CLA 2019-09-06 16:09:46 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.